01:35
<MikeSmith>
Domenic: the updates you made to https://developer.mozilla.org/en-US/docs/Web/API/Document/domain look great
06:31
<MikeSmith>
annevk: I realize now some links were broken by the e-mail ↠ email change I made
06:33
<MikeSmith>
example: was https://html.spec.whatwg.org/multipage/forms.html#e-mail-state-(type=email) but now https://html.spec.whatwg.org/multipage/#email-state-(type=email)
06:34
<MikeSmith>
I think it would be good if I fixed at least some of those
06:35
<MikeSmith>
...by adding back some anchors with the old fragment IDs
06:35
<MikeSmith>
I discovered the #e-mail-state-(type=email) one due to MDN having had a link to that fragment
06:36
<MikeSmith>
...and I already fixed the MDN link
06:36
<MikeSmith>
but of course there are likely links to that anchor in quite a few other places
09:13
<annevk>
MikeSmith: oh, maybe we should revert the MDN fix and just only keep the old ID working?
09:30
<anurag>
Hi, apologies if this is not the correct medium for this. I was interested in understanding HTMl standard and started at "Loading web pages". There I found an example stating that the following code snippet:
09:30
<anurag>
```
09:30
<anurag>
const popup3 = window.open();
09:30
<anurag>
popup3.close();
09:30
<anurag>
```
09:32
<anurag>
I am sorry for half a message. I am trying to understand how to send a message here.
10:17
<JakeA>
annevk: I'll ask about the openWindow thing
10:17
<annevk>
thanks, it seems we have some internal test that could potentially be converted...
10:17
<annevk>
JakeA: also, where there security issues related to openWindow?
10:18
<JakeA>
annevk: not that I'm aware of
10:18
<JakeA>
We might also have tests to upstream. I'll find out.
10:18
<JakeA>
I mean, it'd be surprising if we didn't
10:55
<croraf>
andreubotella, and others
10:55
<croraf>
https://github.com/heycam/webidl/issues/923
11:15
<JakeA>
annevk: we don't have good test coverage for openWindow, just https://source.chromium.org/chromium/chromium/src/+/master:content/browser/service_worker/service_worker_clients_api_browsertest.cc;l=134;drc=919ce657e4e37dfa13758f1eb8fe0e9ef7ab1b20;bpv=0;bpt=1, so if you have stuff that can upstreamed, that'd be great
13:25
<ondras>
a question regarding use-CORS-preflight flag. say I have a "POST /a" request that results in a preflight, succeeds and results in a http/303 redirection. the preflight flag is set, so the following "GET /b" still triggers the OPTIONS preflight. is this intentional?
16:00
<annevk>
ondras: we could maybe consider changing that, but doing that check again now the method changed and maybe some headers are dropped feels a bit dangerous
16:30
<ondras>
annevk: I see. so not really intentional, there does not seem to be a particular reason for that, just an implementation consequence that is a bit inconventient now
16:30
<ondras>
*inconvenient
16:37
<annevk>
ondras: yeah, it also predated explicitly requiring changing the method and such
16:45
<ondras>
annevk: okay, thanks