WHATWG
2023-06-06
plaintext logs
prev next
source on github
00:34
<ntim>
Hi! can someone help merge this editorial typo fix: https://github.com/whatwg/html/pull/9388 ?
08:13
<annevk>
Jake Archibald: note that className is already defined on Element as I pointed out earlier; I guess SVG overrides it, though you could probably use the other one if you really wanted to
08:15
<Jake Archibald>
annevk: when did you previously point that out? (Or do you mean `classList`?)
08:19
<annevk>
Jake Archibald: I pointed out in the issue that it's defined in DOM so the request should maybe be tracked there
08:20
<annevk>
Jake Archibald: don't blame you for missing it though, there's a lot of noise :-)
08:22
<Jake Archibald>
annevk: ahh I did see that, but I didn't join the dots to "it's on `Element`"
08:22
<Jake Archibald>
But yeah, that makes sense
08:46
<Jake Archibald>
annevk: happy to move it to DOM, but I figured it'd be better to wait until there's general "let's do it for className and htmlFor" agreement, then split it into two issues
10:50
<annevk>
Ms2ger: how does the Wasm CG render proposals relative to the main spec? Like https://github.com/WebAssembly/gc/issues/376 makes a bunch of changes to the main spec and then I guess the main spec is occasionally merged back in or some such? But is the result rendered somewhere?
11:10
<Ms2ger>
annevk: yeah, proposals are done in a fork of the main spec repo, which is merged into it occasionally. The result is rendered if someone managed to get the CI working
11:13
<Ms2ger>
Example: https://webassembly.github.io/content-security-policy/js-api/#host-ensure-can-compile-wasm-bytes
11:37
<sideshowbarker>
annevk: yeah, proposals are done in a fork of the main spec repo, which is merged into it occasionally. The result is rendered if someone managed to get the CI working
I've been asked to fix that CI. So I just need to make time to go in and do it. Next week at the earliest
11:38
<Ms2ger>
You have?
11:38
<sideshowbarker>
Yeah, by PLH
11:39
<sideshowbarker>
My understanding is that the former team contact set up that build?
11:39
<sideshowbarker>
And that it's... a bit baroque? Idiosyncratic
11:40
<Ms2ger>
I think you're talking about the .rst → W3C-styled HTML build
11:41
<sideshowbarker>
Ah
11:41
<sideshowbarker>
To be honest, I haven't even looked at any of it yet
11:42
<sideshowbarker>
PLH told me long ago some stuff had stopped working there
11:43
<sideshowbarker>
But I as yet have zero idea of the specifics
11:44
<sideshowbarker>
Regardless, I'd be glad to help good whatever's busted
11:45
<sideshowbarker>
In particular whatever bits are the ones Eric had been taking care of
11:45
<Ms2ger>
This isn't the thing Eric did, but since you offered, https://github.com/WebAssembly/js-types/issues/23 has been ignored for the last 2.5 years
11:47
<sideshowbarker>
Well that's a long time
11:47
<sideshowbarker>
I will go in and take a look
11:50
<sideshowbarker>
The reason I'm good at fixing strangely engineered builds that are broken is that I'm good at strangely engineering them to begin with myself, and breaking them
12:06
<Ehsan Azari>

Is there any EventSource (or EventSource-like) web api for client/browser side communications?
I mean having event sources in client/browser side too, to consume those client/browser-side events when is needed mainly client/browser side (and maybe even from server-side?)

I mean following the philosophy of EventSource and EventTarget for both client/browser and server sides
To me it seems that EventSource and EventTarget come from those old days when just server was the event source

13:14
<annevk>
sideshowbarker: 🎉
13:25
<Ehsan Azari>
Isn't a good idea to have event sources on client/browser side too?
16:16
<smaug>
annevk: in https://fetch.spec.whatwg.org/#fetch-groups, the last sentence, should it be "and keepalive", not "or keepalive" ?
16:42
<Ehsan Azari>
annevk: in https://fetch.spec.whatwg.org/#fetch-groups, the last sentence, should it be "and keepalive", not "or keepalive" ?
It looks correct with or
It allows for either condition to be true for the associated fetch record's controller to be terminated
18:55
<smaug>
but we don't want to terminate keepalives, no?
21:38
<annevk>
smaug: yeah, that looks wrong, file an issue?
21:39
<annevk>
smaug: seems to have been wrong since I first drafted this concept: https://github.com/whatwg/fetch/commit/744d8b3bbe3b59492cff5f0fdd49b8dd053c4571
21:52
<smaug>
https://github.com/whatwg/fetch/issues/1669
23:39
<Anton Maliev>
Hey folks, question on the Storage spec. I'm trying to get a callback for every site that accesses any form of non-cookie storage. Looking at the spec https://storage.spec.whatwg.org/, which is the best algorithm to monkey patch? I'm considering "obtain a storage bottle map / shelf / key", but I'm not clear on the flow. Are these called once the first time an origin accesses local or session storage, and never before then? Could the browser run them for a non-site reason?