00:45
<Domenic>
freddy: There is unfortunately nothing good for that purpose. If you create something please let us know!
00:46
<Domenic>
Is there any particular reason for defining these methods on the Node interface?
Probably because they used to work on or accept Attr nodes, many years ago. We could move them to ParentNode now but that would not really improve things in an interesting way. (It would change the type of exception thrown and change various feature-tests like 'insertBefore' in Attr which I'm not aware of anyone using.)
01:35
<gollones>
hello how can i recieve sms without a mobile
08:59
<smaug>
NavigateEvent is becoming so weird
09:00
<smaug>
having methods on Events is in general weird antipattern
09:31
<Domenic>
I get that that is your opinion, but I don't think it's shared...
10:39
<nicolo-ribaudo>

Hello everyone! I'm reading the various script fetching algorithms, and I have a question.
What's the reason for setting Request.destination for import statements in workers to "worker", but setting it to "script" for dynamic imports?

This can be also tested in Chrome with https://request-destination-playground.glitch.me/, running

new Worker(`data:text/javascript, import 'https://cdn.skypack.dev/has';`, { type: "module" });

and

new Worker(`data:text/javascript, await import('https://cdn.skypack.dev/has');`, { type: "module" });

in the console