Re: [editing] change of event names beforeInput -> beforeEdit -> beforeInput? (#87)

> while the same code and the same version of Firefox would not fire on another Mac OS X laptop.

If so, it's a bug of Firefox. But if it's really existing, Firefox's many features are broken, e.g., incremental search in various UI, autocomplete in form fields. So, I cannot believe there is such odd bug unless I see some bug reports with STR.

> The event seemed unreliable, which was also a contributing factor in us not wanting to mess with it.

input event is the only way to handle something immediately after text is modified in an editor at least for now. Therefore, it must be used in a lot of websites.

Therefore, even if some spec will define input event as deprecated, browsers keep supporting it for compatibility.

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/editing/issues/87#issuecomment-137356380