- From: Johannes Wilm <notifications@github.com>
- Date: Mon, 26 Jun 2017 00:06:33 -0700
- To: w3c/uievents <uievents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 26 June 2017 07:07:09 UTC
As part of the TAG review of the Input Events spec, it [was mentioned](https://github.com/w3ctag/design-reviews/issues/160#issuecomment-298142881) that the beforeinoput event would be useful also for inoput elements. That has of coruse been the point already, but it does not seem clear from the spec under what circumstances the events are actually fired. In the UI Events spec, it says: "Input events are sent as notifications whenever the DOM is being updated." That seems too broad -- when some JavaScript triggers a DOM change, that should not trigger beforeinput/input events. In the [current editor's draft](https://w3c.github.io/input-events/index.html) of the Input events spec it says: "Input events are sent before (beforeinput event) and after (input event) a user attempts to edit the markup. This includes insertion and deletion of content, and formatting changes. Input events are dispatched on elements that act as editing hosts, including elements with the contenteditable attribute set, textarea elements and input elements that permit text input." Could we come up with a text that we can all agree on? -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/uievents/issues/145
Received on Monday, 26 June 2017 07:07:09 UTC