00:55
<smaug>
Why allow-same-origin is called allow-same-origin?
00:55
<smaug>
when "same" doesn't really refer to anything
01:23
<zcorpan_>
smaug: it's more "make-same-origin" i guess? but allow- is consistent with the other values
01:23
<smaug>
it doesn't make anything same origin
01:24
<smaug>
it is more like "dont-make-unique-origin"
01:24
<zcorpan_>
yes, right
01:24
<smaug>
or keep-origin
01:24
<zcorpan_>
but this is shipped, so too late to bikeshed the name :-)
01:30
<smaug>
true. just an example of a very confusing name
05:18
<annevk>
So when does w3c-test update relative to when a PR lands? Still not updated it seems…
05:20
<annevk>
I think allow-same-origin makes sense, it's about whether the frame can communicate with its own origin
05:32
<zcorpan>
annevk: maybe the sync is broken? earlier today i added w3c-test:mirror in a PR and didn't see it appear on w3c-test.org. MikeSmith?
07:51
<annevk>
Yeah, I think it must be, unless it's usual for there to be a delay of days
07:51
<annevk>
I don't really use w3c-test.org much
07:52
<jochen__>
annevk: what would the issue be about?
07:53
<jochen__>
annevk: "please spec how resources from css are fetched"?
07:53
<annevk>
jochen__: multiple issues sounds good
07:53
<annevk>
jochen__: one exactly like that
07:53
<annevk>
jochen__: and the other, about them providing a way to talk about the style attribute's styles specifically
07:54
<annevk>
jochen__: it just seems good manners to file issues you have with them, they might not know about their shortcomings
07:55
<jochen__>
fair enough
07:55
<jochen__>
I think I figured out a way to talk about style attributes btw
07:56
<jochen__>
there's CSSATTR, and that also talks about how to resolve base URLs for those styles
07:56
<jochen__>
so it looks like there are stylesheets where the base url is defined
07:56
<jochen__>
and then there are styles that are created via CSSATTR that defines a link to the styled element (and therefore an owner document)
07:57
<jochen__>
and then there are styles that HTML creates for presentation attributes, and there HTML does the URL processing, so it can as well provide the referrer with it
08:01
<annevk>
That depends on how you implement presentation attributes
08:01
<annevk>
An implementation could implement them through CSS extensions
08:10
<jochen__>
https://github.com/w3c/csswg-drafts/issues/904
08:11
<jochen__>
annevk: that wouldn't change the fact that implementation created the styles
09:28
<MikeSmith>
annevk: https://platform.html5.org/ cert invalid?
09:35
<annevk>
MikeSmith: strange
09:36
<MikeSmith>
yeah now got stranger even
09:36
<MikeSmith>
now shows a message from Dreamhost saying Site Not Found
09:39
<annevk>
MikeSmith: I'm not sure what's going on
09:41
<annevk>
MikeSmith: filed a ticket, seems to affect all of html5.org
09:41
<annevk>
MikeSmith: but not any of my other domains
09:46
<MikeSmith>
oh
09:47
<MikeSmith>
ah not https://checker.html5.org/ at least, since that’s different
09:49
<annevk>
MikeSmith: yeah, that's a DNS entry on html5.org, I guess those still work
09:50
<MikeSmith>
yeah
09:57
<MikeSmith>
botie, inform zcorpan yeah the w3c-test.org sync script is failing. Will try to get it fixed today (and get the backlog synced too)
09:57
<botie>
will do
10:39
<miketaylr>
annevk: thanks for inlining the image!
10:40
<miketaylr>
i mean, i guess i have to backdoor the spec some other way now
10:40
<miketaylr>
>:|
11:20
<annevk>
miketaylr: I knew it!
13:12
<nox>
/old-tests/submission/Opera/script_scheduling/096.html seems to be wrong.
13:12
<nox>
It expects defer scripts to not have ran before DOMContentLoaded.
13:13
<annevk>
nox: I guess the original creation date of that resource is long gone, but I would not be surprised if it predates the specification
13:14
<nox>
Yes. :)
13:14
<nox>
annevk: I like the indentation too.
13:15
<nox>
annevk: It's also duplicated, 098.html is the same.
13:15
<nox>
Because why not.
13:23
<annevk>
It's something annoying that a lot of questions about IDL need to be answered in part by the "overload resolution algorithm"
13:23
<annevk>
somewhat
13:44
<nox>
annevk: Is it me, or the spec for <script> doesn't actually specify that when adding a document fragment to a node that is in a document, any scripts in that fragment should be executed *after* all nodes in the document fragment are moved into the document?
13:46
<nox>
annevk: Which seems to be a prerequisite for 147.html to succeed, that is.
13:48
<nox>
Firefox passes 147.html, Safari doesn't.
13:49
<nox>
Chrome does.
13:49
<nox>
Anyone with Edge can test?
14:17
<annevk>
nox: ask jst for a BrowserStack account, but I can run a test for you
14:17
<botie>
will do
14:18
<annevk>
nox: and yes, that's the intent of how DocumentFragment insertion works, did we finally define it?
14:18
<annevk>
nox: I kinda forgot whether that was specified already
14:18
<nox>
annevk: No.
14:18
<nox>
annevk: It just says to call the insertion steps on each inserted node.
14:19
<annevk>
nox: ah, https://github.com/whatwg/html/issues/1127
14:19
<annevk>
I filed it, but didn't really do anything with it yet
14:20
<nox>
Ok.
14:20
<annevk>
nox: link of the test?
14:20
<nox>
annevk: There is something else to take into account to,
14:20
<nox>
annevk: nested scripts in a DocumentFragment.
14:20
<nox>
annevk: I filed https://github.com/whatwg/html/issues/2265 earlier.
14:20
<annevk>
I guess I'll mark that as a duplicate then
14:20
<nox>
The nested thing is covered by 128.html.
14:21
<nox>
https://github.com/w3c/web-platform-tests/blob/master/old-tests/submission/Opera/script_scheduling/128.html#L31
14:21
<nox>
Firefox expects #3 before #2.
14:22
<nox>
annevk: I fixed 128.html in the Servo fork: https://github.com/servo/servo/pull/15011/commits/4593b7c1d61773efe4e1c634190a9f7b72471b9c#diff-30743df3600624bb8b533c45a97cd12b
14:23
<annevk>
nox: Edge throws for 147
14:24
<annevk>
nox: can't get parentNode from null/undefined
14:24
<nox>
annevk: Yeah that's what Safari says too.
14:35
<annevk>
nox: is that what you get if you don't implement some kind of double insertion loop?
14:36
<annevk>
I guess it's considered some kind of safety feature so you can't manipulate the DocumentFragment?
14:37
<nox>
annevk: What do you mean?
14:37
<nox>
annevk: Whether scripts are executed at insertion time or not, they are not in the fragment anymore.
14:37
<nox>
Oh never mind, I got what you mean.
14:37
<nox>
annevk: Yeah I feel like we need two loops.
14:37
<nox>
annevk: Didn't we use to have two loops actually?
14:37
<nox>
I remember doing something like that, but that was probably another part of the spec.
14:41
<annevk>
nox: I don't think I ever defined the hooks necessary in DOM, but HTML might have alluded to it somehow
14:42
<annevk>
nox: you want two loops for safety?
14:42
<nox>
annevk: No, for proper ordering.
14:43
<nox>
annevk: HTML specifies when to prepare a script in a way that seems to want to cover that case but fails at it, at least that's my impression.
14:45
<annevk>
Proper ordering?
14:46
<benjamingr>
Domenic / caitp / bterlson if I could steal 5 minutes from anyone who could help me work on test262 that would be great
14:46
<benjamingr>
working onhttps://github.com/tc39/proposal-async-iteration/issues/69 and I want to make sure I'm in the right track
14:46
<annevk>
benjamingr: you might want to ping in #jslang on Mozilla IRC
14:46
<annevk>
benjamingr: in case anyone else is around that can help
14:47
<benjamingr>
Thanks, that's useful advice
14:48
<nox>
annevk: Proper ordering of operations. To make 147.html correct with regard to the spec.
14:53
<annevk>
nox: well the spec is "wrong" and 147 is way old, so I'm not sure what proper means
14:53
<annevk>
nox: but if it just means what Gecko implements, sure
14:53
<nox>
annevk: Yeah, that's what I meant. :D
16:51
<annevk>
MikeSmith: DreamHost is suggesting html5.org is only down locally somehow
16:51
<annevk>
MikeSmith: that it might be a DNS problem or some such, they can apparently access it fine
16:52
<boogyman>
When trying to access it via chrome canary, i get a message that u
16:52
<boogyman>
"usual or incorrect credentials" are being returned
16:52
<annevk>
MikeSmith: I guess I'll wait a little longer as they suggested
16:53
<annevk>
boogyman: you don't get "Your connection is not private"?
16:53
<boogyman>
I do, and upon expanding for more details, that's the message in the "fine print"
16:55
<annevk>
Ah, yeah, it seems we're getting a wrong certificate
16:57
<annevk>
Oh god, caniuse.com doesn't verify its JSON before publishing so now the HTML Standard refuses to build
17:03
<annevk>
Or maybe the request timed out?
17:05
<annevk>
Yeah that is what's happening
17:18
<botie>
zcorpan, at 2017-01-13 09:57 UTC, MikeSmith said: yeah the w3c-test.org sync script is failing. Will try to get it fixed today (and get the backlog synced too)
17:20
<Domenic>
Yeah GitHub was down for 10 minutes or so
17:23
<annevk>
Good, build is passing again
17:38
<benjamingr>
Domenic: almost done with what we could
17:39
<Domenic>
benjamingr: awesome. How can I best help? It seems like the checklists are still pretty scattered; did anyone ever set up an editable checklist or trello board or similar?
17:40
<benjamingr>
We did all the method tests, and copied what AsyncFunction does in builtins, and added the missing expression/declaration tests.
17:42
<benjamingr>
We don't have a checklist set up
17:45
<benjamingr>
I'll squish so you can take a look at the changes
18:44
<terinjokes>
anyone know the likelihood that SRI will be extended to other resources, such as images?
19:24
<Domenic>
mkwst would know
23:28
<tobie>
Are there examples of web specs which use internal slots and the this.[[slot]] notation beyond streams?
23:41
<Domenic>
web payments has a few
23:41
<Domenic>
web bluetooth and usb i beleive
23:46
<TabAtkins>
Font Loading