-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Product Pull Request] fix: make iframe wrapper take all vieport width #268
Comments
Thanks for your submission, @openedx/open-edx-project-managers will review shortly. |
Original PR: Resolves openedx/xblock-drag-and-drop-v2#312. Probably it was introduced in openedx/frontend-app-learning#27. Consider how the block interface behaves in the legacy courseware (Lilac): 2023-04-02.16-46-58.mp4 Here is how it behaves in this MFE: 2023-04-02.16-49-45.mp4 With changes from this PR: 2023-04-02.16-54-47.mp4 Testing instructions It's not related to this PR's changes, but possibly to this: openedx/frontend-app-learning#414 |
@cablaa77 This one is for product review. For some reason I can't move the screenshots over from the original PR, so you can see them here. openedx/frontend-app-learning#1094 |
Hi @cablaa77, could you provide a rough estimate on when we can expect product feedback for this feature? |
Hi @jmakowski1123 @cablaa77 @Daniel-hershel, what can we do to get product review started for this feature? CC: @0x29a for openedx/frontend-app-learning#1094 |
@itsjeyd I came across this PR and decided to look into it. I noticed something on the final video posted on 1094. At 0:00, the course navigation fills the whole viewport width: But, at 0:29 the navigation is narrower than the viewport width: Is this expected behaviour? Would it be possible for the navigation to fill the entire wrap? Other than that, the update looks great to me! |
@ali-hugo, this is not expected, but I think it's a separate bug. I mentioned it in the "Misc notes" section of the PR, but perhaps should have added more details: |
Thanks a lot @ali-hugo! |
@ali-hugo Thank you for the review here! 👍 @jmakowski1123 Will @ali-hugo 's review be binding, ie will be sufficient to complete the product review, and allow the PR to merge once the issues fixed? Or will it still require a product review? |
(Side note for additional context: openedx/edx-platform#31715 hasn't gone through engineering review yet. So regardless of who gets to provide final/binding approval from product perspective, there will be one more step to complete before we can merge it.) |
@ali-hugo Is this good from your side now and if so, would you mind leaving an explicit approval? Depending on @jmakowski1123's input on @antoviaque's question above, we might still need another 👍 from product, but it would be good to know if you have any additional feedback for @0x29a to address. |
@jmakowski1123 I just noticed that the info about related PRs in the issue description might need updating? In particular, the following parts seem to be referencing a different feature and PR than openedx/frontend-app-learning#1094:
|
Great, thanks for the quick reply @ali-hugo 🎉 |
Hey @jmakowski1123, when you get a minute would you mind having a look at these questions: |
@itsjeyd, the PR is merged now. Should we change the label and close this issue? |
@Agrendalath Updating feature tickets on the Open edX Roadmap board is currently out-of-scope for OSPR management, so I'll let @jmakowski1123 handle this part. @jmakowski1123 Happy to ping someone else from the product team if that's what you'd prefer; just let me know. (In the meantime I did change the label from |
Closing as this is marked "Shipped" on the PR board 🎉 |
Abstract
For Contributing Author:
This is the Primary Product Ticket for the following community contribution: Add a toggle to allow redirecting to courseware after enrollment
Checklist prior to undergoing Product Review:
The following information is required in order for Product Managers to be able to review your pull request:
Only if necessary:
Related PRs
For Product Manager doing the review:
What criteria should be analyzed from Product to approve a PR?
The text was updated successfully, but these errors were encountered: