01:29
<MikeSmith>
what spec actually requires that the Origin header be sent for any request that is not a GET or HEAD request?
01:29
<MikeSmith>
I see the Fetch spec says this:
01:29
<MikeSmith>
A CORS request is an HTTP request that includes an Origin header. It cannot be reliably identified as participating in the CORS protocol as the Origin header is also included for all requests whose method is neither GET nor HEAD.
01:30
<MikeSmith>
…but the Fetch spec itself nowhere requires that Origin be sent in any request that is not a GET or HEAD request
02:04
<MikeSmith>
ah nm
02:04
<MikeSmith>
found it
02:04
<MikeSmith>
https://fetch.spec.whatwg.org/#dfnReturnLink-20
02:04
<MikeSmith>
> If the CORS flag is set or httpRequest’s method is neither `GET` nor `HEAD`, then append `Origin`/httpRequest’s origin, serialized and UTF-8 encoded, to httpRequest’s header list.
09:00
<XhmikosR>
does anybody know if there's any downside in using ceche immutable?
09:00
<XhmikosR>
*cache
09:01
<annevk>
XhmikosR: you need to change URLs whenever you update the resource
09:01
<XhmikosR>
annevk: I already need to do that in the time my cache is valid which is too long already :)
09:01
<annevk>
XhmikosR: then you should be fine I think
09:02
<XhmikosR>
so my question should be, if one has cache busting and long cache headers, does immutable have any downsides?
09:02
<XhmikosR>
I see, thanks. I wanted to give immutable a go
11:17
<tobie>
In Bikeshed, How would I link to the Audio named constructor of in HTML spec? {{Audio}} doesn't seem to work.
11:18
<tobie>
s/of in/in the/
11:23
<annevk>
tobie: you'd have to PR HTML to export it appropriately
11:23
<tobie>
annevk: ty
14:20
<Ms2ger>
annevk, rs? https://github.com/w3c/testharness.js/pull/238
14:22
<Ms2ger>
Or foolip ^
14:23
<annevk>
Ms2ger: looks okay, do we really still need ArrayClass to exist at all?
14:23
<annevk>
Ms2ger: I thought we could remove that, or did I forgot about something silly?
14:24
annevk
can't find any GitHub issues
14:24
<foolip>
Ms2ger, annevk: I merged it
14:25
<Ms2ger>
annevk, cssom still uses it, for better or worse
14:25
<Ms2ger>
Takk
14:25
<annevk>
Ms2ger: can't CSSOM use iterable<>?
14:25
<Ms2ger>
No comment
14:25
<annevk>
I can't find a single issue so I'm just going to raise one against IDL
14:28
<annevk>
Ms2ger: https://github.com/heycam/webidl/issues/291
14:28
<Ms2ger>
Thanks
17:37
<foolip>
No Hixie here? annevk, what is the canonical pronunciation? what wee gee?
17:38
<annevk>
foolip: I use it
17:38
<foolip>
annevk: then I will too. I've alternated between what wig and what double-u gee.
17:39
<foolip>
(and what ve ge in Swedish)
17:40
<foolip>
annevk: working on bit.ly/blinkon7-wpt
17:42
<annevk>
foolip: Domenic uses wig
17:43
<annevk>
foolip: are things recorded? Some talks seem very interesting
17:43
<foolip>
annevk: yes they are, but it seems like videos aren't available immediately after, might take a few days
17:44
<foolip>
I'm going to claim that the goal of standards is roughly "Maximize throughput of interoperably implemented spec text"
17:44
<foolip>
Does that seem sane?
17:58
<Domenic>
foolip: I think also the goal of allowing followers (including late followers like Servo) is important.
18:00
<foolip>
Domenic: absolutely. but if we have 4 interoperable implementations, is it not quite likely that the spec and tests are in good shape for a new entry?
18:01
<foolip>
s/entry/enterer/?
18:04
<annevk>
Yeah, converge impls, enable competition
18:05
<annevk>
Not sure what maximize throughput means exactly, sounds like streams terminology
18:06
<foolip>
heh, it's just the utilitarian in me
18:07
<foolip>
oh, I see what you mean with streams, this is probably confusing phrasing
18:07
foolip
will tinker
18:10
<Domenic>
bz to the rescue in that confusing origin/domain thread, yay
18:11
foolip
finds a recent blog post with the wording already tinkered
18:42
<annevk>
Domenic: maybe you can prod some people in person for the <canvas> blogpost
18:43
<Domenic>
Oh yeah
18:46
<annevk>
Domenic: kinda want it to include pretty graphics now, but we probably shouldn't ask for too much
22:22
<Domenic>
rniwa: haven't confirmed myself but we have reports that Safari also fails on emoji custom element names: https://bugs.chromium.org/p/chromium/issues/detail?id=687678