зеркало из https://github.com/mozilla/gecko-dev.git
498c3f96b9
Unfortunately, there is no official way to detect whether browser supports or not `beforeinput` event in the wild because Chromium does not support `onbeforeinput` event handler attribute. On the other hand, we're the last browser vendor which does not support `beforeinput` event, and we make `InputEvent.getTargetRanges()` enabled only when `beforeinput` event because it returns meaningful value only when the event type is `beforeinput`. So, web apps can detect `beforeinput` event support with checking type of or existence of it instead. However, in our experience, it's guessed what a lot of web apps check whether "Firefox" or not to consider whether it can use `beforeinput` events. If so, we need to announce shipping `beforeinput` event and the way to feature detection before actually shipping it. Otherwise, we wouldn't get enough feedback from testers. First of all for shipping `beforeinput` events, we should collect how much web apps which use `HTMLEditor` use `beforeinput` event when it's enabled, and how much web apps use mutation events or mutation observer instead of `beforeinput` events even when it's enabled. Honestly, I'd like to collect URLs which don't use `beforeinput` event, but use mutation events or mutation observer. But it's really sensitive data so that I believe that we shouldn't collect it. Differential Revision: https://phabricator.services.mozilla.com/D92548 |
||
|---|---|---|
| .. | ||
| composer | ||
| libeditor | ||
| reftests | ||
| spellchecker | ||
| txmgr | ||
| AsyncSpellCheckTestHelper.jsm | ||
| moz.build | ||
| nsIDocumentStateListener.idl | ||
| nsIEditActionListener.idl | ||
| nsIEditor.idl | ||
| nsIEditorMailSupport.idl | ||
| nsIEditorObserver.idl | ||
| nsIEditorSpellCheck.idl | ||
| nsIHTMLAbsPosEditor.idl | ||
| nsIHTMLEditor.idl | ||
| nsIHTMLInlineTableEditor.idl | ||
| nsIHTMLObjectResizer.idl | ||
| nsITableEditor.idl | ||