This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Firefox, Chrome and IE on Windows and Firefox, Chrome and Safari on Mac fire input event after compositionend event. So, I believe that this event order should be defined in D3E spec.
In addition, we should be including beforeinput as well. I've updated section 5.2.7.6 "Input Events During Composition" based on our previous discussion (https://docs.google.com/document/d/1pGo9hmOXCu71lnpXbqpTQNQP70DU9E-1tNN3yEWg5ig/edit?usp=sharing): ----------------+------------------------------------------------ compositionend | ----------------+------------------------------------------------ beforeinput | Sent only if we’re about to update the DOM. | Cancelling this will prevent the update and | the input event. ----------------+------------------------------------------------ | If DOM was not updated during composition, | it is updated now ----------------+------------------------------------------------ input | Sent only if the DOM was updated. ----------------+------------------------------------------------ Please review that section when you get a chance.
Current implementations, compositionend is just a notification. I.e., DOM change occurs before compositionend. Therefore, dispatching beforeinput after compositionend feels strange to me.