New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 675820 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Jan 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 2
Type: Bug

Blocking:
issue 701863



Sign in to add a comment

InputEvent: Track if we could fire 'beforeinput' after 'compositionupdate'

Project Member Reported by chongz@chromium.org, Dec 20 2016

Issue description

This is the chromium side tracking for https://github.com/w3c/uievents/issues/66.

Current spec defines event order:
1. 'beforeinput'
2. 'compositionupdate'
3. DOM Update
4. 'input'

However we need to check if we can change the order to be:
1. 'compositionupdate'
2. 'beforeinput'
3. DOM Update
4. 'input'

 

Comment 1 by chongz@chromium.org, Mar 15 2017

Blocking: 701863

Comment 2 by chongz@chromium.org, Mar 15 2017

Blocking: -585875

Comment 3 by chongz@chromium.org, Jan 11 2018

Status: WontFix (was: Assigned)
InputEvent has went into stable for some time and it's unlikely we are going to change it.
Mark as WontFix.

Sign in to add a comment