- From: Masayuki Nakano <notifications@github.com>
- Date: Fri, 01 Feb 2019 01:34:57 -0800
- To: w3c/uievents <uievents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 1 February 2019 09:35:19 UTC
Ccing @garykac Currently, UI Events [defines](https://w3c.github.io/uievents/#keypress-event-order) event order of "keypress" event is: 1. `keydown` 2. `beforeinput` 3. `keypress` 4. `input` 5. `keyup` However, **both** Chrome and Safari uses this event order: 1. `keydown` 2. `keypress` 3. `beforeinput` 4. `input` 5. `keyup` Even for Firefox, the latter event order makes sense too because Firefox implements each user operation in editor is a default action of `keypress` event. So, if Firefox needs to conform to current draft's event order, Mozilla need to rewrite event handling a lot. So, both backward compatibility with Chrome/Safari and for implementing `beforeinput` quicker on Firefox, I'd like to suggest that the event order should be changed in the UI Events. -- 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/220
Received on Friday, 1 February 2019 09:35:19 UTC