Input losing focus when wrapped into label
See original GitHub issueObserved on Firefox 31 if the input that gets enhanced with typeahead is wrapped into a <label>
tag it will focus and blur again right away.
Issue Analytics
- State:
- Created 9 years ago
- Reactions:1
- Comments:13 (2 by maintainers)
Top Results From Across the Web
In React ES6, why does the input field lose focus after typing a ...
While using Chrome's Inspector, it looks like the whole form is being re-rendered instead of just the value attribute of the input field...
Read more >focus-within - CSS: Cascading Style Sheets - MDN Web Docs
The :focus-within CSS pseudo-class matches an element if the element or any of its descendants are focused. In other words, it represents an ......
Read more >css Archives - Coding Beauty
Keep label on top when non-empty input loses focus. There's one more thing we have to do. When you enter text in the...
Read more >Focusing: focus/blur - The Modern JavaScript Tutorial
Losing the focus generally means: “the data has been entered”, so we can run the code to check it or even to save...
Read more >Binded input loses focus on typing - Google Groups
The problem is that with every change to the model object the ng-repeat regenerates the whole array and so blurs your input box....
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 FreeTop 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
Top GitHub Comments
My workaround is to back out be9114d after setting up the typeahead. That commit seems to be an IE8/IE9 fix and luckily we’re not supporting those:
Thanks @ebi for the detective work. Nice find.
Unbelievable there’s a bug like this! Drove me crazy for at least half an hour. 2014 when the issue has 1st been raised, still no fix? Sad.
To date, still broken, using Safari 11.0 (12604.1.38.1.7) on macOS Sierra (10.12.6).