05:17
<annevk>
Jake Archibald: it tests that foO gets through Access-Control-Allow-Methods: foO, which doesn't work for the same reason I think
05:22
<Jake Archibald>
annevk that test would pass if the ACAM check was case insensitive. Chrome is currently allowing methods that the server didn't allow, which seems bad 😬
05:27
<Jake Archibald>
Ah, Hiroshi has tests for that https://github.com/web-platform-tests/wpt/pull/29680/files#diff-1166b97b413b5886babae2b10bae70526b1b9ff70b5feeb3c658177a2fa3f556R79
05:33
<annevk>
Those look good!
06:48
<sideshowbarker>
And to merge "Obsolete features" back into the main body of the specification
If we move the Obsolete Features content, we should make sure to preserve the IDs ー because MDN has links to some of it
06:51
<sideshowbarker>
This is another reason why I don't think MDN should be linking to any spec parts about obsolete content to begin with, and why I never added such links myself. But others see it differently, so we do have a few of those in MDN
06:56
<annevk>
sideshowbarker: interesting, kinda surprising MDN cares about them indeed, but we should preserve IDs anyway as source code or bug comments are likely to link it too
07:02
<sideshowbarker>
The main thing I can think of is to split each element section into two sections, one for authors and one for implementers
Big +1 to that. Whatever we can do to further clearly separate author-conformance requirements from implementor requirements is a win for everybody
11:11
<hsivonen>
Last night, an ominous though occurred to me, but, fortunately, things are OK: https://hsivonen.com/test/moz/meta/after-head-variable-with-crlf.php?start=1023 and https://hsivonen.com/test/moz/meta/after-head-variable-with-crlf.php?start=1024 . (For a moment I though that WebKit and Blink might counting after CRLF normalization. Fortunately not.)
18:15
<Domenic>
Jake Archibald: perhaps we can store an opaque flag on the history entry that would avoid revealing it in those cases?
This seems useful for solving the concerns in https://github.com/WICG/app-history/issues/71 where our tentative conclusion was that pages marked with no-referrer would become opaque to app history.
18:19
<Domenic>
https://github.com/whatwg/html/issues/7116#issuecomment-928659511 -- I couldn't find the issue about clarifying document conformance requirements vs UA conformance requirements now, but did we conclude how to deal with cases like this?
https://github.com/whatwg/html/issues/5461
18:19
<zcorpan>
thanks
18:25
<wanderview>
Domenic: aren't you on vacation?