07:11
<sideshowbarker>
Thanks for the heads-up. Yes, please, if you can restore the timestamps.json file, I’d much appreciate it. Without the old Last-Revised header — and with the Last-Modified header not showing the actual publication date — there’s otherwise no good way programatically, from client code, to determine the dates of the published specs. (That is, without resorting to parsing or scraping the HTML from a response, or running a git command to check when the last update was made to the corresponding git source).
09:22
<sideshowbarker>

Andreu Botella: I don’t know you’re aware already, but the spec build for the unversioned CSS specs is currently broken. I think Tab has an idea how to fix it and may just need to make time to do that once he’s back online — but in the meantime maybe you have some insight on an elegant way to get it working again, given the current state of things.

And the current state of things appears to be that drafts.csswg.org is now just proxying w3c.github.io/csswg-drafts — while requests to w3c.github.io/csswg-drafts are now redirecting to drafts.csswg.org — but only partially. (How that setup is actually working at all, I don’t really understand yet.)

The related build changes are in https://github.com/w3c/csswg-drafts/commit/52077ef4b1b0459f2aef3179dcf47a6c3e185012 and https://github.com/w3c/csswg-drafts/commit/8523f13a005f7213c39200e24944f8549e9e5227, and what’s partial about the redirect behavior is this:

At https://github.com/w3c/csswg-drafts/issues/8798#issuecomment-1536775277 Tab mentions it'd be a bunch of trouble to get the redirects for the unversioned spec URLs working. But since I think you originally wrote the build code, it seems possible you might have some idea of how to do it with less trouble.

10:35
<Andreu Botella>

Andreu Botella: I don’t know you’re aware already, but the spec build for the unversioned CSS specs is currently broken. I think Tab has an idea how to fix it and may just need to make time to do that once he’s back online — but in the meantime maybe you have some insight on an elegant way to get it working again, given the current state of things.

And the current state of things appears to be that drafts.csswg.org is now just proxying w3c.github.io/csswg-drafts — while requests to w3c.github.io/csswg-drafts are now redirecting to drafts.csswg.org — but only partially. (How that setup is actually working at all, I don’t really understand yet.)

The related build changes are in https://github.com/w3c/csswg-drafts/commit/52077ef4b1b0459f2aef3179dcf47a6c3e185012 and https://github.com/w3c/csswg-drafts/commit/8523f13a005f7213c39200e24944f8549e9e5227, and what’s partial about the redirect behavior is this:

At https://github.com/w3c/csswg-drafts/issues/8798#issuecomment-1536775277 Tab mentions it'd be a bunch of trouble to get the redirects for the unversioned spec URLs working. But since I think you originally wrote the build code, it seems possible you might have some idea of how to do it with less trouble.

I wasn't aware, I haven't really been keeping track of what was going on with the spec builds. But let me take a look
11:12
<timdream>
Is the event firing order on the same node spec’d anywhere? I saw a blog post saying that the language regarding event firing order (“… in their order of registration.”) was present in the UI Event level 3 draft around 2011 but removed in 2016.
It was indeed not explained in the currenct UI Event spec, but the section on “changes from DOM level 2” did mention the event listeners is now ordered.
I am very confused by that blog post…
Post: https://blog.gslin.org/archives/2023/05/08/11176/
Current UI Event draft: https://w3c.github.io/uievents/#event-flow
11:15
<Domenic>
What do you mean "event firing order"? Do you have a code example?
11:28
<timdream>
What do you mean "event firing order"? Do you have a code example?
el.addEventListener(e => console.log("a")
el.addEventListener(e => console.log("b")
el.addEventListener(e => console.log("c")
el.dispatchEvent(new Event("test"))
11:29
<timdream>
Should console always print a,b,c per spec?
11:31
<Domenic>
Yes. This is specified in https://dom.spec.whatwg.org.
11:33
<timdream>
Domenic: could you point me the section? Sorry I couldn’t find it.
11:34
<Domenic>
https://dom.spec.whatwg.org/#dispatching-events
11:35
<timdream>
https://dom.spec.whatwg.org/#dispatching-events
Wonderful, thank you!
18:26
<TabAtkins>
sideshowbarker: Both unversioned symlinks and the timestamps.json file are back in place, lmk if anything is still wonky on your end.
22:55
<Richard Gibson>

what happens if an author does something like this:

function generateBid(foo, bar, baz, setBid) {
  Promise.resolve()
    .then(() => setBid("post hoc"));
}

an exception?