Consume user activation when creating a new top-level traversable

[CanadaHonk]

Closes #10108.

• At least two implementers are interested (and none opposed):
  • Mozilla
  • Chromium (already implemented)
• Tests are written and can be reviewed and commented upon at:
  • HTML: Consume user activation for window.open (multi-global test) web-platform-tests/wpt#49138
  • https://bugzilla.mozilla.org/show_bug.cgi?id=1879820
• Implementation bugs are filed:
  • Chromium: Already has this behavior except the global is wrong in the multi-global test: https://issues.chromium.org/u/1/issues/379674022
  • Gecko: https://bugzilla.mozilla.org/show_bug.cgi?id=1879820
  • WebKit: https://bugs.webkit.org/show_bug.cgi?id=283318
• MDN issue is filed: already documented in https://developer.mozilla.org/en-US/docs/Web/Security/User_activation#transient_activation (for window.open)
• The top of this comment includes a clear commit message to use.

(See WHATWG Working Mode: Changes for more details.)

---

/document-sequences.html ( diff )

[zcorpan]

I think this looks reasonable. It will only consume when actually creating a top-level traversable.

[EdgarChen]

WPT tests will be added in https://bugzilla.mozilla.org/show_bug.cgi?id=1879820.

[annevk]

Thanks! @zcorpan can you complete OP?

[zcorpan]

The multi-global test highlights a difference between this PR and what is implemented in Chromium.

currentNavigable is set by

2. Let sourceDocument be the entry global object's associated Document.
3. Let targetNavigable and windowType be the result of applying the rules for choosing a navigable given target, sourceDocument's node navigable, and noopener.

https://html.spec.whatwg.org/#window-open-steps

So the user activation is consumed in the entry global. But Chromium consumes in the relevant global per: web-platform-tests/wpt#49138 (comment)

I think using the entry global makes sense if other things of the window open steps use that (as currently defined).

[zcorpan]

Thanks! @zcorpan can you complete OP?

Done.