Floating label won't float if input is disabled (even if it contains value)
See original GitHub issueThere’s an edge case where floating label won’t float if input is disabled even if it contains value. The result is that the label stays over the input value.
The reason is that :valid
doesn’t “work” if the input is disabled.
Maybe we should implement a quasar-textfield
component that handles blur events, or maybe is there some other way by just changing the default floating state (by using :not(:valid)
and :not(:disabled)
).
Issue Analytics
- State:
- Created 7 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Floating label not working when required attribute removed
When you remove required part of your CSS no longer applies. I removed input:not(:focus):valid ~ .floating-label and it works again.
Read more >How to build a floating label input field - ITNEXT
It doesn't take into account if the input has a value. Our label will also currently overlap any placeholder text in the field....
Read more >Input label does not move up when value or placeholder is sp
I am trying to use mdbootstrap in my meteor app but am running into issues with forms: the label does not move above...
Read more >Float Labels with CSS
It's an input that appears as if it has placeholder text in it, but when you click/tap into that input, that text moves...
Read more >Floating labels are problematic. After writing Placeholders are…
Floating labels typically have small text, so that as it floats, ... Animation, even if it's done well, could be distracting and ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Will be available in v0.14
Thanks for reporting this. Will fix it really soon.