This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 25291 - Should define input event should be fired after compositionend
Summary: Should define input event should be fired after compositionend
Status: RESOLVED FIXED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: HISTORICAL - DOM3 Events (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Gary Kacmarcik
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 25288
  Show dependency tree / graph
 
Reported: 2014-04-08 08:00 UTC by Masayuki Nakano
Modified: 2014-04-16 01:19 UTC (History)
2 users (show)

See Also:

Attachments

Description Masayuki Nakano 2014-04-08 08:00:37 UTC 
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.
Comment 1 Gary Kacmarcik 2014-04-15 23:41:23 UTC 
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.
Comment 2 Masayuki Nakano 2014-04-16 01:19:44 UTC 
Current implementations, compositionend is just a notification. I.e., DOM change occurs before compositionend. Therefore, dispatching beforeinput after compositionend feels strange to me.