01:57
<Domenic>

Since Resource-Hints has been archived and now points to HTML, it's not clear to me if dynamically inserted <link rel="prefetch"> are supposed to work or if only the ones in the initial parsing would? It used to be explicitly stated

The resource hint link's [...] MAY be dynamically added to and removed from the document.

It was even one of the use-cases in that document.

Did I just miss where the current specs would allow that? I was hoping for allowed in body to say something related but even looking at that I didn't find anything conclusive.

I think prefetch is missing "appropriate times to fetch and process". Maybe file a bug? Noam Rosenthal will probably fix it quickly :)
01:58
<Kaiido>
Ok. Will do later today.
01:59
<Domenic>
Still lots of open issues for https://github.com/whatwg/html/issues?q=is%3Aopen+is%3Aissue+label%3A%22topic%3A+link%22 sadly
02:00
<Domenic>
Although several of the older ones are mostly-fixed but have comments at the bottom saying "here's what remains to be fully 100% sure we've figured out this entire area"
04:30
<Noam Rosenthal>
I think prefetch is missing "appropriate times to fetch and process". Maybe file a bug? Noam Rosenthal will probably fix it quickly :)
Oh darn, I have a clear memory of me writing that bit but it must have been deja-vu from other link types. CC me on the filed bug Kaiido !
09:25
<annevk>
zcorpan: ping on https://github.com/html5lib/html5lib-tests/pull/163
23:37
<zcorpan>
ack
23:38
<zcorpan>
https://twitter.com/mutherpluckinb/status/1538852415331500038 is a good point. Is it possible to pass on a user activation with postMessage?
23:38
<Jeffrey Yasskin>
We had a proposal for that... <looks for it>
23:41
<Jeffrey Yasskin>
https://twitter.com/mutherpluckinb/status/1538852415331500038 is a good point. Is it possible to pass on a user activation with postMessage?
https://chromestatus.com/feature/5574000088449024
23:42
<zcorpan>
Jeffrey Yasskin: thx
23:44
<Jeffrey Yasskin>
Oh, but it's still alive and shipped in Chrome as https://wicg.github.io/capability-delegation/spec.html
23:46
<Jeffrey Yasskin>
The difference is that each capability has to be specified separately, as opposed to delegating activation itself.
23:48
<zcorpan>
Jeffrey Yasskin: right, the feature url is https://chromestatus.com/feature/5708770829139968