-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
Migrate to beforeInput #7462
Comments
Order of things:
|
FYI: Firefox supports https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Releases/87 https://developer.mozilla.org/en-US/docs/Web/API/HTMLElement/beforeinput_event#browser_compatibility |
hi, any progress here? |
The same problem is occurring in Japanese. |
hi, any progress here? |
There's been a lot of work put in this ticket in the past, but then we had to stop for about 1 year. The good news is that we restarted the work 🎉 . However, we continue in a new ticket to have a clearer picture of where we are because a lot of things happened in the meantime. The new ticket is #11438 and I'm closing this one. |
📝 Provide a description of the improvement
AFAICT https://bugzilla.mozilla.org/show_bug.cgi?id=970802 and https://bugzilla.mozilla.org/show_bug.cgi?id=1449831 landed in Firefox 76. That means that we can replace the current mutation-based typing handling with
beforeInput
🎉.It'd probably be good to keep the mutation handler for environments that do not support
beforeInput
yet, even if we don't officially support them (probably older versions of FF or Safari). On all environments that supportbeforeInput
we should use it, though.The goal is to use
beforeInput
to handle:As next steps we can also consider using it as an additional trigger for:
Some additional issues that might get fixed with it:
beforeInput
support detectionbeforeInput
eventbeforeInput
eventbeforeInput
beforeInput
types across the featuresbeforeInput
types across the features (list, horizontal line, etc.)If you'd like to see this improvement implemented, add a 👍 reaction to this post.
The text was updated successfully, but these errors were encountered: