-
Notifications
You must be signed in to change notification settings - Fork 46.8k
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
Bug: Firefox Android not triggering onSelect in <input> when dragging cursor #25643
Comments
I believe something in here needs to be changed. There's a comment saying:
But according to Firefox documentation it's not true: https://developer.mozilla.org/en-US/docs/Web/API/HTMLInputElement/selectionchange_event |
I've been trying to fix this and I can't get the event triggered on the input node to even reach the SelectEventPlugin.js |
This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment (for example, "bump"), and we'll keep it open. We are sorry that we haven't been able to prioritize it yet. If you have any new additional information, please include it with your comment! |
Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please create a new issue with up-to-date information. Thank you! |
React version:
Steps To Reproduce
Link to code example: https://codepen.io/AndreasBBS/pen/ExRgdgN (codesandbox was down at the moment I was testing this)
The current behavior
Firefox:
Record_2022-11-07-02-39-11.mp4
The expected behavior
Chrome/Brave:
Record_2022-11-07-02-40-48.mp4
Extra Details
This seems to have to do with how Firefox implements the
selectionchange
event for inputs. According to this documentation, firefox fires theselectionchange
event on the input node instead of on document. In fact, if you try the little snippet they have in the documentation you'll find that it only works on Firefox and not any other browser.I'm not sure if other browsers are gonna move in this direction, but if they do, this bug will become more common. Chrome already has a bug report and if they 'fix' it, this behavior will also happen there.
The text was updated successfully, but these errors were encountered: