|input| and |beforeinput| were only brought into D3E because they were 1) Required since |keypress| was being deprecated (with |input|/|beforeinput| intended as a replacement) 2) Not being worked on by anyone.
>From that POV, it sounds like a reasonable idea. Esp. since one of the places (IIRC) where we thought it was supposed to be was in the Editing spec. However, the biggest issues we had with |beforeinput| and |input| was determining the correct event order relative to composition and keyboard events. So it seems like a cross-dependency for D3E to depend on the Editing spec to get |input| and |beforeinput| and for the Editing spec to need D3E's composition and keyboard events (to properly specify the event ordering). Thus, I wonder if a separate Input Event spec (that both D3E and Editing would refer to) would make more sense. As for "easier to finish DOM L3", that depends. D2E defines keypress, which is being deprecated in favor or input/beforeinput. Thus, D3E will not be a complete functional replacement for D2E without a proper spec for input/beforeinput. -Gary On Mon, Dec 8, 2014 at 2:05 PM, Ben Peters <ben.pet...@microsoft.com> wrote: > Since the Editing Task Force is working on several input-related issues, > we would like to take over the work on Input Events. I have created an > unofficial document for that purpose at > http://w3c.github.io/editing-explainer/input-events.html. It is based on > the work in DOM L3. Can we move the DOM L3 Input Events design to be only > what is already implemented in browsers (which should make it easier to > finish DOM L3, right?), and work on it going forward in the Editing Task > Force? > > > > Ben >
