-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
fix: advanced editor styling on library authoring [FC-0076] #36146
base: master
Are you sure you want to change the base?
fix: advanced editor styling on library authoring [FC-0076] #36146
Conversation
Thanks for the pull request, @rpenido! This repository is currently maintained by Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are ready for engineering review.
|
<!-- Built-in XBlocks (and some plugins) depends on LMS CSS --> | ||
<link rel="stylesheet" href="{{ lms_root_url }}/static/css/lms-course.css"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For the editor iframe, the lms-course.css
caused some issues.
I didn't find where this was used to check the results, but the Unit Outline and the Course View seem okay.
We can't add this conditionally if needed.
@rpenido These changes look and work fine within the legacy studio editor :) However from the MFE, the nested scrollables are pretty awkward -- maybe make the editor modal a bit taller to accommodate the full iframe, and remove the outer nested scrollbar? Advanced.editor.style.fixes.-.Made.with.Clipchamp.mp4 |
Thanks for the input, @pomegranited! It took me some time, but I think I won the scrollbars battle! |
Almost.. it's working fine for Drag & Drop, but:
Maybe the templates for these XBlocks could be modified to remove the outside scrollable area? I think it'd be fine if we have to scroll down to the Save/Cancel/Add+ buttons like we do for Drag & Drop. Also: Since we've got editing capability for all of these advanced block types now, shouldn't we update frontend-app-authoring's |
Hi @pomegranited! Can you share what you are seeing? I didn't manage to reproduce it here. editor-modal.mp4
For me, the Drag & Drop also has the buttons always at the bottom of the dialog. Are you experiencing something different?
That makes sense to me. What do you think @ChrisChV? Are there other requirements to make it active by default? |
I think we need to finish the task of creating the advanced blocks before changing the default values of |
Totally fine to wait for this. I just wanted to make sure this config change is on your list :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 My apologies @rpenido , my CSS must have been cached! They're working fine now.
Google docs is a little weird, since its modal is larger than its edit page:
But the rest look and work great.
- I tested this using the PR test instructions.
- I read through the code
- I checked for accessibility issues by using my keyboard to navigate
-
Includes documentationN/A -
User-facing strings are extracted for translationN/A
@@ -136,6 +136,9 @@ | |||
LMS_ROOT_URL = f"http://{LMS_BASE}" | |||
FEATURES['PREVIEW_LMS_BASE'] = "preview.localhost" | |||
|
|||
CMS_BASE = "localhost:8001" | |||
CMS_ROOT_URL = f"http://{CMS_BASE}" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@rpenido I think CMS_ROOT_URL
is a new env variable, right? I think we should add it in cms/envs/common.py
, in cms/envs/production.py
. What do you think?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure! Done here: f92d488
@rpenido Do you think it's easy to fix this issue on this PR? No problem if it's not easy, it can be done in a follow-up task |
It is not an easy fix unless we include some hardcoded min-height to match the heights. I'm unsure if this is a good idea.. |
@rpenido Thanks! I will merge it tomorrow morning |
Description
This PR fixes the styles for the advanced editors (poll, survey, LTI Provider, etc).
LTI Consumer
Survey
Google Document
Additional Information
Testing Instructions
tutor dev exec cms npm run build-dev
to compile the Sass filesPrivate ref: FAL-4012