Currently, Input Events Level 2 and UI Events define that beforeinput event should be fired before compositionupdate and input event should be fired after compositionupdate. However, under current design, it's difficult to do that (with current design, beforeinput would be fired after compositionupdate). One of the reason of difficult to change this behavior is, we handle composition with DOM "text" event which is not in any standards and not implemented by any other browsers. So, if we'd be able to remove it, I'd be very happy, but we need to collect number of event listeners in the web.
5 months ago
"text" event is Mozilla specific event, not in any standards. The event follows "compositionupdate" event and editor modifies composition string when receives the event in the system group. So, we'd like to stop dispatching this unnecessary event but we need to get actual usage in the web.
chutten: Could you review this data collection? Now, the patch has already gotten r+. So, you'd be easy to check the patch rather than only with my broken English text.
Attachment #9024928 - Flags: review?(chutten)
Comment on attachment 9024928 [details] bug1506434.txt DATA COLLECTION REVIEW RESPONSE: Is there or will there be documentation that describes the schema for the ultimate data set available publicly, complete and accurate? Yes. Standard Telemetry mechanisms apply. Is there a control mechanism that allows the user to turn the data collection on and off? Yes. Standard Telemetry mechanisms apply. If the request is for permanent data collection, is there someone who will monitor the data over time? N/A, expires in Firefox 67. Using the category system of data types on the Mozilla wiki, what collection type of data do the requested measurements fall under? Category 1, Technical. Is the data collection request for default-on or default-off? Default-on, all channels. Does the instrumentation include the addition of any new identifiers (whether anonymous or otherwise; e.g., username, random IDs, etc. See the appendix for more details)? No. Is the data collection covered by the existing Firefox privacy notice? Yes. Does there need to be a check-in in the future to determine whether to renew the data? Yes. :masayuki is responsible for renewing or removing this metric before it expires in Firefox 67. --- Result: datareview+
Attachment #9024928 - Flags: review?(chutten) → review+
Pushed by firstname.lastname@example.org: https://hg.mozilla.org/integration/autoland/rev/02a5b2ef21e9 Add telemetry probe to collect how percentage users meet web apps which listens "text" event r=smaug
You need to log in before you can comment on or make changes to this bug.