-
Notifications
You must be signed in to change notification settings - Fork 70
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: Background Description was required but not always saved #55
Fix: Background Description was required but not always saved #55
Conversation
df2fc66
to
ef50f19
Compare
@dianakhuang Can you please provide a second review for this PR too? (next week is OK if you're not available this week). This (and the first PR I also just pinged you on) are some follow-up fixes to bugs found after #34 merged. FWIW, the first two bugs in this PR were introduced during the a11y review on #34, after you'd already given thumbs up. |
Looks good 👍 |
@mtyaka I just pulled in one more one-line workaround, FYI - it was already on the sandbox. Without that fix, newly-added drag and drop components do not load in Studio until you refresh the page. We need this workaround until https://github.com/edx/edx-platform/pull/11433 is reviewed and merged. |
@@ -283,6 +283,7 @@ function DragAndDropBlock(runtime, element, configuration) { | |||
if (!window.gettext) { window.gettext = function gettext_stub(string) { return string; }; } | |||
|
|||
var $element = $(element); | |||
element = $element[0]; // <- workaround Studio bug until https://github.com/edx/edx-platform/pull/11433 is merged |
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.
It looks like the edx-platform PR merged, so I don't think you need this workaround anymore.
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.
@dianakhuang Do you think it's ok if we leave it in for a while though, in order to preserve Dogwood compatibility? We have clients who are using this block on Dogwood.
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.
I think it's fine to leave it in for compatibility reasons, but in that case, it'd be nice to have the comment updated to reflect exactly what needs to happen before it can be removed. I might be helpful to write the new comment as a // TODO:
as well to make it easier to find later and let people know that it's an action that should be taken later.
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.
Great, makes sense. I will update the comment accordingly before merging this.
Other than that, 👍 |
f6c39b9
to
6920dc2
Compare
Thanks for the review, @dianakhuang ! I've updated that comment and rebased. Will merge once the build is green. |
Fix: Background Description was required but not always saved
This PR fixes the following bugs with the new drag and drop component:
href="#"
event was not prevented).JIRA: YONK-264 / SOL-1642
Sandbox: http://studio.master.dndv2.sandbox.opencraft.com/ and http://master.dndv2.sandbox.opencraft.com/ (shared by a few different open PRs, but it does currently include the changes from this PR)