1459231 - [meta] Follow the spec better regarding activation behavior

Status: NEW

(Core :: DOM: Events, enhancement, P2)

Description

[Olli Pettay [:smaug][[e-mail]]]

Need to review the spec and check where we don't follow it

Comment 1

[PhistucK]

This related to, or blocking bug 588927.

Also, see https://bugs.chromium.org/p/chromium/issues/detail?id=912892#c8 - an interoperability issue reported to Chrome that seems to be a Firefox and Edge (irrelevant at this point) issue -
Basically, when two activation targets are nested <button><label>a</label></button>, Firefox picks the outermost element (<button>), Chrome picks the innermost element (<label>).

Interestingly, Edge diverged from Internet Explorer (which behaved like Chrome).

Comment 2

[Vincent Hilla [:vhilla]]

This should be resolved with my changes for bug 1658996.

Comment 3

[Vincent Hilla [:vhilla]]

I just noticed that dispatching DOMActivate for button and input (code) should probably be part of activation behavior. Though we should look at when other browsers dispatch it.

Edit: here is a test, this works as expected

data:text/html,<button id=btn>test</button><script>btn.addEventListener("DOMActivate", e=> console.log(e.eventPhase))</script>