07:58
<yoav>
annevk: I'm looking into adding the initiator to the `<link rel=prefetch>`/`<link rel=prerender>` processing model
07:59
<yoav>
The best place seems to be https://html.spec.whatwg.org/multipage/semantics.html#obtaining-a-resource-from-a-link-element
08:00
<yoav>
but, it probably requires some "else if" logic, as `<link rel="preload prefetch">` is a possible value
08:01
<yoav>
any examples for similar language for "else if" in the spec?
08:01
<annevk>
yoav: "Otherwise, if X, ..."
08:02
<yoav>
ok, coo
08:02
<yoav>
l
09:37
<yoav>
annevk: https://github.com/whatwg/html/pull/3353
09:38
<yoav>
(also the participation bots are rightfully angry with me. Waiting for a decision on https://github.com/whatwg/participate.whatwg.org/issues/11)
09:40
<annevk>
yoav: I thought you agreed with me that we wanted separate initiators?
09:41
<yoav>
I guess I did...
09:42
<yoav>
let me find the relevant discussion...
09:44
<annevk>
It's actually quite hard to find all elements that have "flow content" as their content model
09:44
<yoav>
https://github.com/w3c/webappsec-csp/pull/283
09:44
<yoav>
OK, updating 659
10:49
<kochi>
Shall we (did we) define clipboard events composed or not?
10:49
<kochi>
(i.e. paste, etc.)
10:53
<annevk>
kochi: I'd say yes, given it's UI input
10:54
<annevk>
kochi: I'm not sure if we carefully considered them; I don't quite recall
10:54
<kochi>
As far as I see no mentions about "composed" flag in clipbard API draft.
10:59
<annevk>
kochi: I looked and per hayato_ we left them out: https://github.com/w3c/webcomponents/issues/513#issuecomment-224468080
11:00
<annevk>
kochi: that basically happened though because nobody took the time to look into it much
11:00
<annevk>
kochi: worth opening an issue for to settle this in a more principled matter
11:05
<kochi>
annevk: thanks for the pointer!
11:05
kochi
will file an issue on clipboard api
11:11
<kochi>
https://github.com/w3c/clipboard-apis/issues/61
15:27
<nox>
annevk: https://twitter.com/nokusu/status/952925077976305668
15:28
<annevk>
nox: bet you wish Twitter would let you edit that
15:28
<nox>
What did I do?
15:28
<nox>
Intra was on purpose.
15:28
<annevk>
nox: the plot thickens
15:28
<nox>
'a prefix signifying inside, within, interior, during'
15:29
<nox>
I was punning, clearly I didn't pun well.
17:36
<Domenic>
tobie: PR preview doesn't seem to be updating on https://github.com/whatwg/html/pull/3352, even a day later. Maybe because of the force-push?
17:37
<tobie>
No. It should work.
17:37
<tobie>
It’s an issue with amazon, apparently.
17:38
<tobie>
And I’m somehow not handling the error message as I should.
17:38
<tobie>
Need to dig in to see what’s up.
17:38
<tobie>
^ Domenic
17:39
<Domenic>
OK np
19:58
<smaug____>
Why https://github.com/w3c/web-platform-tests/blob/master/shadow-dom/event-composed-path-with-related-target.html#L136 is valid?
19:58
<smaug____>
Isn't that against step 4 in https://dom.spec.whatwg.org/#concept-event-dispatch
20:00
<smaug____>
looks like Safari has the same interpretation what I have
20:00
<smaug____>
https://wpt.fyi/shadow-dom/event-composed-path-with-related-target.html
20:01
smaug____
fixes the test
20:03
<smaug____>
hayato_: FYI ^
20:03
<smaug____>
kochi: ^
21:20
<tobie>
Domenic: ok, so it's the caching layer for whatpr.org that is causing the issue
21:33
<tobie>
Domenic: now to understand what part of AWS does what…
23:49
<tobie>
foolip, Domenic: so the issue was that amazon cloud front (which is used for whatpr.org) caches pages that don't have cache-control directives, contrary to what S3 does.
23:50
<TimothyGu>
cloudfront is the CDN, which I guess isn't terribly surprising
23:50
<tobie>
foolip, Domenic: I wiped out those caches for HTML, and regenerated the intersection of open PR and existing caches for HTML.
23:52
<tobie>
foolip, Domenic: LMK if you bump into the issue again
23:53
<tobie>
TimothyGu: yeah, I wrongly assumed consistency with S3