-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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 mismatching link control action buttons visual order and DOM order #56042
Conversation
Size Change: -34 B (0%) Total Size: 1.7 MB
ℹ️ View Unchanged
|
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.
Tested this and the code change makes sense, thank you!
As an unrelated separate note, while testing it felt surprising the tabbing was not constrained in the popover (at least in Firefox). I am just talking about perception in my case not some rule I expected 😄
@draganescu thanks for reviewing.
Yeah, this is something that has always been a bit controversial. I think there was some reasoning about not constraining tabbing within these 'inline' popovers. However, many things have changed since then. RIght now, the situation is very mixed and largely inconsistent. Most popovers in the UI outside of the post content do implement constrained tabbing. Some popovers that can be accessed from the post content (e.g. the link edit) do not. Now that these popovers are rendered outside of the post content iframe I think they should all implement constrained tabbing. In fact, tabbing away from these popovers brings users very farm from they originally were (inside the post content). |
#56042) * Fix visual and dom order by using HStack. * Fix padding of tertiary buttons within the visual editor. * Fix top padding in media replace popover.
Fixes #56039
What?
First pass at fixing the mismatching visual and DOM order of the 'Cancel' and 'Save' buttons in the link control UI.
Why?
For accessibility, visual order and DOM order must always match.
It is important to make all designers and developers aware of this. Pinging all the folks who worked on #46933
Cc @getdave @draganescu @jameskoster @richtabor @scruffian @jasmussen @joedolson @SaxonF
How?
Uses the
HStack
component instead of custom CSS rules. This makes these Cancel/Save buttons consistent with all similar button paris in use in the edifor, for example in the:Testing Instructions
Additionally:
Testing Instructions for Keyboard
See above.
Screenshots or screencast
Before:
After: