Weird focus-event related problem after upgraded to 0.47.0
See original GitHub issueHi everyone. I just encountered a weird focus-event related problem after I upgraded the react-datepicker
to 0.47.0. I tested the following steps on both Chrome and Firefox and it seems both browsers get the same problem. Here are the simple steps to reproduce the problem:
- Open https://hacker0x01.github.io/react-datepicker/
- Scroll down to “Default” example. Left click the datepicker input box, then select a random date.
- Press “tab” key on the keyboard.
Then you will see the browser enters a dead loop and keeps switching between the two datepicker input box.
The problem is gone after downgraded to 0.46.0.
Any idea why this problem happened? I checked the comparison between 0.46.0 and 0.47.0 but didn’t find anything interesting.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:4
- Comments:5 (2 by maintainers)
Top Results From Across the Web
FocusEvent.relatedTarget - Web APIs | MDN
The FocusEvent.relatedTarget read-only property is the secondary target, depending on the type of event:
Read more >office-ui-fabric-react - UNPKG
Any props values will override state, but will not update internal state. If prop is defined\n * and then later undefined, state will...
Read more >manuel - npm
A super customizable VDOM autocomplete with *production ready* defaults.. Latest version: 0.66.0, last published: 5 years ago.
Read more >New Arm Tumbleweed snapshot 20210929 released!
Drop pkgconfig(dbus-1) BuildRequires following upstream changes. - Update URL and Source to new home, as intel have dropped maintenance of this package, ...
Read more >Changes.20181018.txt
Following upstream changes, pass docs=true and introspection=true to meson. ... Update to version 2.57.2: + Require pcre 8.31 and meson 0.47.0.
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
I should also mention that I can recreate the issue with 0.46.0 by not selecting a random date.
EDIT: @philiptzou called me out on this (thank you, bud) -I was doing something else different. I was using a custom input component, though I was omitting the
onKeyDown
event handler. My entry point was different but I think the assessment of the loop still holds.This fix is released. Let me know if this happens again.