25291 2014-04-08 08:00:37 +0000 Should define input event should be fired after compositionend 2014-04-16 01:19:44 +0000 1 1 1 Unclassified WebAppsWG HISTORICAL - DOM3 Events unspecified All All RESOLVED FIXED P2 normal --- 25288 1 masayuki garykac mike www-dom public-webapps-bugzilla oldest_to_newest 103551 0 masayuki 2014-04-08 08:00:37 +0000 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. 103919 1 garykac 2014-04-15 23:41:23 +0000 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. 103931 2 masayuki 2014-04-16 01:19:44 +0000 Current implementations, compositionend is just a notification. I.e., DOM change occurs before compositionend. Therefore, dispatching beforeinput after compositionend feels strange to me.