| 06:17 | <MikeSmith> | > MikeSmith: given the triviality of the feature, a proper spec would be very procedural |
| 06:17 | <MikeSmith> | I somehow didn’t notice that statement til now |
| 06:19 | <MikeSmith> | kind of once again leaves me at a loss for words |
| 06:23 | <MikeSmith> | gonna be fun to read the Interoperability and Compatibility section of that imminent Intent to Ship |
| 14:51 | <annevk> | MikeSmith: why so mean-spirited? |
| 15:18 | <MikeSmith> | annevk: yeah I was out of line |
| 15:19 | <MikeSmith> | not been in the best of spirits |
| 15:20 | <MikeSmith> | mounir: sorry for my comments |
| 15:20 | <MikeSmith> | not meant to denigrate the work |
| 15:38 | <mounir> | MikeSmith: np |
| 18:31 | <othermaciej> | mounir, MikeSmith: what's the "6.3 Activation" that explainer refers to? |
| 18:35 | <othermaciej> | I guess that it's referencing the HTML spec (probably correctly) |
| 20:24 | <annevk> | MikeSmith: 👍❤️ |
| 22:21 | <MikeSmith> | othermaciej: yeah https://html.spec.whatwg.org/multipage/interaction.html#activation though it’s not clear to me how what’s described in https://github.com/WICG/gesture-delegation/blob/master/explainer.md#new-html-concept would actually fit into that section |
| 22:23 | <othermaciej> | MikeSmith: it would require defining a new notion of "sticky activation" |
| 22:23 | <MikeSmith> | ok |
| 22:23 | <othermaciej> | I am not sure any of this quite makes sense though, because other browsers do not have an autoplay policy that works like Chrome's |
| 22:23 | <othermaciej> | Safari does not grant sticky autoplay permission until you navigate outside the current eTLD+1 |
| 22:24 | <othermaciej> | nor do we intend to |
| 22:24 | <othermaciej> | this whole "explainer" is designed around Chrome's very specific autoplay behavior which is not anyone else's |
| 22:25 | <MikeSmith> | oh |
| 22:26 | <MikeSmith> | might be worth (re)stating that as an issue at https://github.com/WICG/gesture-delegation/issues |
| 22:28 | <othermaciej> | I am not sure how seriously to take a WICG explainer document. Easier to comment when there's actual spec language proposed for a real spec. |
| 22:29 | <othermaciej> | I should check if I am a member of WICG. Can't remember any more. |
| 22:32 | <othermaciej> | wow there is a lot of stuff up in WICG github |
| 22:49 | <MikeSmith> | othermaciej: yeah, and at least a couple things that have moved on to working groups, like IntersectionObserver |
| 22:50 | <MikeSmith> | oh, and the PaymentRequest API started out in the WICG repo |
| 23:10 | <Domenic> | othermaciej: well there is a Chrome intent to ship based on this explainer so, I guess semi-seriously. |
| 23:12 | <othermaciej> | I don't think what is described in the explainer would work for Safari, the one other browser that I know of having autoplay restrictions. Also the attribute name is horrific. But we do need a similar feature for our similar (but not identical) autoplay policy. |
| 23:12 | <othermaciej> | Is an issue against the Explainer the best way to communicate this? |
| 23:14 | <othermaciej> | I'm not even sure our user-action-to-play policy is sticky per page, I will have to ask (we changed it a few times) |
| 23:19 | <MikeSmith> | othermaciej: either an issue against the Explainer or a comment at https://discourse.wicg.io/t/proposal-for-a-gesture-delegation-api/2340 I guess |
| 23:23 | <MikeSmith> | or reply to the Intent to Ship at https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/F4h7sdBdiBM |
| 23:24 | <othermaciej> | Chromium intent to ship is definitely not my circus or my monkeys |
| 23:24 | <othermaciej> | I asked the folks who worked on this to remind me of Safari's exact behavior, so I'll try to file an issue |
| 23:30 | <othermaciej> | In the meantime I filed name bikeshed issues |