Conversation
add "pointer-events none" to pseudo-element same as twbs#37359
|
Thanks for this PR @jonnysp. Indeed sounds better with this modification. |
|
@julien-deramond it is not for the read only label. |
|
@mdo @patrickhlauke regarding this. We better be consistent here and make sure we still follow a11y best practices. |
|
the problem isn't present on the current https://getbootstrap.com/docs/5.3/forms/floating-labels/ ... so I'm wondering what changes were introduced that caused the problem in the first place. there's also something funky happening with disabled form fields https://deploy-preview-38023--twbs-bootstrap.netlify.app/docs/5.3/forms/floating-labels/#disabled |
|
FYI there was a conflict between several fixes on the floating labels between the v5.2.3 and v5.3.0-alpha1. Some use cases are broken in https://twbs-bootstrap.netlify.app/docs/5.3/forms/floating-labels/ (issues and PRs exist for that). IMHO the main issue that I can see here in this PR is about the read-only rendering where we can see the "selection" cursor when the labels are hovered even if we can't select their text (which is not the case in our main branch): The other use cases seemed to be enhanced when I looked at them the other day with an extended clickable area (possible to click on the upper area of the input to "enable" the input). |
yeah sorry, what I meant is: i understand that, and am wondering if it's worth investigating how to resolve those conflicts at source, rather than trying to now just patch this one aspect with |



add "pointer-events none" to pseudo-element
same as #37359
Description
Motivation & Context
Type of changes
Checklist
npm run lint)Live previews
Before
https://deploy-preview-38008--twbs-bootstrap.netlify.app/docs/5.3/forms/floating-labels/
After
https://deploy-preview-38023--twbs-bootstrap.netlify.app/docs/5.3/forms/floating-labels/
Related issues