Fix case for event dispatch mutiple after stopPropagation

Fix case for event dispatch mutiple after stopPropagation

https://www.w3.org/TR/DOM-Level-2-Events/events.html says: "Once an event's stopPropagation method has been called, further calls to that method have no additional effect". But it doesn't define if stopped event should be resumed when being dispatched again. While this works on firefox. 

Case is from
http://w3c-test.org/dom/events/Event-dispatch-multiple-stopPropagation.html

BUG=656839

[xing.xu, 2016-10-15 07:37:01]

The CQ bit was checked by xing.xu@intel.com to run a CQ dry run

[commit-bot: I haz the power, 2016-10-15 07:37:11]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[xing.xu, 2016-10-15 08:24:28]

Description was changed from

==========
Fix case for event dispatch mutiple after stopPropagation

https://www.w3.org/TR/DOM-Level-2-Events/events.html
says: "Once an event's stopPropagation method has been
called, further calls to that method have no additional
effect". That means after stopPropagation, you can not
dispatch the same event any more, thus it can not be
received.

Case is from
http://w3c-test.org/dom/events/Event-dispatch-multiple-stopPropagation.html

BUG=651744
==========

to

==========
Fix case for event dispatch mutiple after stopPropagation

https://www.w3.org/TR/DOM-Level-2-Events/events.html says: "Once an event's
stopPropagation method has been called, further calls to that method have no
additional effect". But it doesn't define if stopped event should be resumed
when being dispatched again. While this works on firefox. 

Case is from
http://w3c-test.org/dom/events/Event-dispatch-multiple-stopPropagation.html

BUG=651744
==========

[xing.xu, 2016-10-15 08:24:28]

xing.xu@intel.com changed reviewers:
+ foolip@chromium.org

[commit-bot: I haz the power, 2016-10-15 10:05:32]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-10-15 10:05:33]

Dry run: This issue passed the CQ dry run.

[xing.xu, 2016-10-15 10:58:29]

PTAL.

[foolip, 2016-10-15 20:28:55]

The currently maintained DOM spec is https://dom.spec.whatwg.org/, please check
what it says is the right behavior here and update the description.

If the test is indeed wrong, it's unfortunately not yet possible to change
web-platform-tests by changing the imported copy in the Chromium tree. Instead,
you'll have to create a pull request on
https://github.com/w3c/web-platform-tests, I am @foolip on GitHub if you want me
to have a look.

https://docs.google.com/document/d/1JgPTyIWmjlXyhyatiZ9A6fSbUQPjCyM26budEY90V...
is a plan for how it might become possible to edit these tests in-place, we'll
announce on blink-dev when we're ready for testing, you might want to be an
early adopter if you tend to work on test failures and spec compliance issues :)

[foolip, 2016-10-15 20:41:26]

On 2016/10/15 20:28:55, foolip wrote:
> The currently maintained DOM spec is https://dom.spec.whatwg.org/, please
check
> what it says is the right behavior here and update the description.
> 
> If the test is indeed wrong, it's unfortunately not yet possible to change
> web-platform-tests by changing the imported copy in the Chromium tree.
Instead,
> you'll have to create a pull request on
> https://github.com/w3c/web-platform-tests, I am @foolip on GitHub if you want
me
> to have a look.
> 
>
https://docs.google.com/document/d/1JgPTyIWmjlXyhyatiZ9A6fSbUQPjCyM26budEY90V...
> is a plan for how it might become possible to edit these tests in-place, we'll
> announce on blink-dev when we're ready for testing, you might want to be an
> early adopter if you tend to work on test failures and spec compliance issues
:)

Took a look, I'm pretty sure the failure is legit and Blink needs to change. At
the end of https://dom.spec.whatwg.org/#concept-event-dispatch it says "Unset
event’s dispatch flag, stop propagation flag, and stop immediate propagation
flag" which doesn't seem to happen. Right before "event->setEventPhase(0)"
(should use Event::kNone) in EventTarget::dispatchEventInternal would be the
place, and similar for IDBEventDispatcher::dispatch.

[xing.xu, 2016-10-18 01:22:14]

Description was changed from

==========
Fix case for event dispatch mutiple after stopPropagation

https://www.w3.org/TR/DOM-Level-2-Events/events.html says: "Once an event's
stopPropagation method has been called, further calls to that method have no
additional effect". But it doesn't define if stopped event should be resumed
when being dispatched again. While this works on firefox. 

Case is from
http://w3c-test.org/dom/events/Event-dispatch-multiple-stopPropagation.html

BUG=651744
==========

to

==========
Fix case for event dispatch mutiple after stopPropagation

https://www.w3.org/TR/DOM-Level-2-Events/events.html says: "Once an event's
stopPropagation method has been called, further calls to that method have no
additional effect". But it doesn't define if stopped event should be resumed
when being dispatched again. While this works on firefox. 

Case is from
http://w3c-test.org/dom/events/Event-dispatch-multiple-stopPropagation.html

BUG=656839
==========