10:04
<keithamus>

Chrome seems to be the only browser which shares user activation across iframes. Is this worthy of filing an issue to discuss or is this well known? /cc smaug

Test case:

data:text/html,<!DOCTYPE html><iframe src="https://www.keithcirkel.co.uk/active-check/"></iframe><iframe src="https://www.keithcirkel.co.uk/active-check/"></iframe>;

Click one of the buttons, in Chrome both will switch to isActive: true - others won't.

10:15
<smaug>
keithamus: so that case about sibling iframes, right?
10:15
<keithamus>
yes exactly.
10:16
<smaug>
Per spec user activation should propagate to ancestors and descendants, I think https://html.spec.whatwg.org/multipage/interaction.html#activation-notification
10:16
<smaug>
and that seems to be what Gecko does
10:16
<smaug>
(if I read the code correctly)
10:18
<smaug>
so is this just a bug in Chrome?
10:19
<keithamus>
https://www.keithcirkel.co.uk/active-check/same-origin.html yes it seems same origin descendants works fine across all
10:19
<keithamus>
So yeah this is perhaps a chrome bug.
10:24
<keithamus>
https://github.com/whatwg/html/issues/9831 looks like canadahonk already reported this one 😅. It's tracked in https://issues.chromium.org/issues/41449756 but seems like some ad tech depends on it?
12:08
<smaug>
or that ad tech would prefer the spec behavior?
14:50
<jarhar>
i recommend commenting on that chrome bug to get mustaq's attention