-
Notifications
You must be signed in to change notification settings - Fork 92
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(NcAction*): complete BiDi support #6507
Conversation
Signed-off-by: Maksim Sukharev <[email protected]>
Signed-off-by: Maksim Sukharev <[email protected]>
/backport to next |
top: auto; | ||
width: 1px; | ||
height: 1px; | ||
overflow: hidden; | ||
z-index: -1; | ||
opacity: 0; |
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.
A general note: opacity: 0
must be redundant.
- If an element is not visible already -
opacity: 0
does nothing - If an element is actually visible -
opacity: 0
hides it from view, but the element still exists and might block interactions or have other unexpected effects
But this element is hidden anyway by the server styles, and both old and new visually hidden approaches are not correct here, so can be properly fixed later.
Hidden input must be in the same place as the visual one. Screen reader will focus and select the real <input>
☑️ Resolves
left: -10000px;
was replaced with different handling, as it might affect scrolling (although we don't have a horizontal one, it seems better to keep native elements within the component area, not outside of screen)🖼️ Screenshots
No visual changes (for LTR)
🏁 Checklist
next
requested with a Vue 3 upgrade