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

Issue 775838 link

Starred by 0 users

Issue metadata

Status: WontFix
Owner:
Closed: Sep 25
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 3
Type: Bug



Sign in to add a comment

Event dispatch steps are not in the same order as spec

Project Member Reported by rakina@chromium.org, Oct 18 2017

Issue description

Chrome Version: 61.0.3163.100 (Official Build) (64-bit)
OS: Linux

The steps of event dispatch post-processing (https://cs.chromium.org/chromium/src/third_party/WebKit/Source/core/dom/events/EventDispatcher.cpp?sq=DispatchEventPostProcess&l=258) is not in the same order as in the spec (https://dom.spec.whatwg.org/#concept-event-dispatch).

Expected:
The event dispatch steps are done in the same order as the spec.

Actual:
In the current code, "Set event’s currentTarget attribute to null." is done before "If target's root is a shadow root, then set event’s target attribute and event’s relatedTarget to null.". Naively moving the step to the right order results in test failures.
 

Comment 1 by kochi@chromium.org, Oct 18 2017

Components: Blink>DOM
Status: Assigned (was: Untriaged)
Description: Show this description
Status: WontFix (was: Assigned)
As the steps have changed again, closing this as WontFix.

Sign in to add a comment