WHATWG
2026-01-27
plaintext logs
prev next
source on github
05:59
<annevk>
nicolo-ribaudo: do you know why step 7.1 of https://html.spec.whatwg.org/multipage/webappapis.html#hostloadimportedmodule never does anything with requested?
07:17
<annevk>
Anyone interested in being the second reviewer of a percent-encoding refactoring? https://github.com/whatwg/url/pull/896
07:28
<nicolo-ribaudo>

Inside the loop it should use requested instead of moduleRequest.

The goal there is "when loading the first moduleRequest of a module, validate all of them first".

07:43
<annevk>
nicolo-ribaudo: are you going to PR or shall I?
07:48
<nicolo-ribaudo>
I can open a PR this afternoon
13:54
<Luke Warlow>
Bit of a random one, but WebIDL currently forbids a trailing comma in extended attribute lists, but WebKit uses this pattern quite extensively. Should we just update the spec to allow that grammar? Servo also seems to support the trailing comma (not sure if it's used), chromium seems to forbid it and I'm not sure about Firefox but I think it forbids it too.
13:56
<Ms2ger>
The WebIDL parsers in Firefox and Servo have a common source, but might have diverged at some point, I suppose
21:01
<sideshowbarker>

Linkedin says Alex Mogilevsky is back at Google now. Would be wonderful if he’s on the Chrome team, but it looks more likely that he might be working on AI stuff. And unsurprising, if so.

“Renowned engineer joins AI team at company X” is more of a “Dog bites man” story these days.
“Renowned engineer joins browser-engine project” would be more of the “Man bites dog” story.

21:16
<sideshowbarker>

…
Some good questions at https://github.com/w3c/webcrypto/issues/167#issuecomment-3807539931 for somebody knowledgeable to chime in and answer —

What happens if the algorithm object has a custom property that, on access, transfers the underlying buffer to a message port. Does that put the object in some kind of bad state? Or if it messes with the prototype?

21:33
<Noam Rosenthal>
Yea I agree with most of the thread that the async wrapping for crypto didn't end up making much sense, especially when in workers. David Benjamin already gave a more thorough answer from Google
21:37
<sideshowbarker>

https://github.com/w3c/webcrypto/issues/167#issuecomment-3807081223 is encouraging, though —

That's not to say I don't agree that we could have (had) a better API, but I'm tempted to think that if we could more or less copy+paste the existing API (without the asyncness and with minor improvements) we could have something useful much faster than having to design & discuss a new API for every primitive individually.

It’s nice to now have an editor for that spec who’s pragmatic and really focused on problem solving — and happy to work with others who have that same point of view.

21:39
<Noam Rosenthal>
Yep, let's ship it