00:16
<akaster>
https://github.com/whatwg/html/issues/11314
04:22
<Domenic>
This just seems like a special case of what I covered in https://github.com/w3c/ServiceWorker/pull/1755#issuecomment-2661941708 , about how we often treat some objects as both their JS/IDL instantiations, and as their browser-process instantiations. It's especially bad for globals like Window, Document, WorkerGlobalScope.
10:21
<annevk>
Yeah I guess the question is if we can make a meaningful improvement here that improves clarity while at the same time not have to maintain all kinds of user-agent remote objects. Perhaps we can have some special kind of indication for what objects can be accessed across the boundary and we could maybe even indicate what state can be accessed in this way.
14:03
<akaster>
it definitely has echoes of that issue.
16:08
<akaster>
is every WorkerGlobalScope's embedder policy always supposed to have the default values for every field? I can't find anywhere in the cross references for https://html.spec.whatwg.org/multipage/workers.html#concept-workerglobalscope-embedder-policy that actually initializes it to anything.
16:12
<akaster>
is there supposed to be some stronger relationship between a worker global scope's policy container and its embedder policy or something?
16:14
<akaster>
oh I think I see. the references to WorkerGlobalScope's embedder policy should instead refer to its policy container's embedder policy
16:14
<akaster>
esp given the FIXME in https://html.spec.whatwg.org/multipage/browsers.html#policy-container to "move other policies into the policy container"
20:32
<@allstarschh>
nicolo-ribaudo: Hi, I'd like to ask a question regarding to the fetch descendants of a module script, https://html.spec.whatwg.org/#fetch-the-descendants-of-and-link-a-module-script, in step 7, "Upon rejection of loadPromise, ...", the spec only handles the [[ParseError]] to the 'error to rethrow', what about other Errors thrown during HostLoadImportedModule, https://html.spec.whatwg.org/#hostloadimportedmodule, for example resolutionError, TypeError
20:33
<nicolo-ribaudo>
I'll reply in the next few days, I need to re-read the spec I wrote because it has been a while
20:39
<@allstarschh>
in step 7.2 of the fetch descendants, "run onComplete given null", then to the 'execute the script element", step 4, if el's result is null, fire onerror
20:41
<@allstarschh>
and the wpt is https://github.com/web-platform-tests/wpt/blob/master/html/semantics/scripting-1/the-script-element/import-attributes/invalid-type-attribute-error.html
20:42
<@allstarschh>
the wpt expects window.onerror, not script's onerror, so I am confused
20:42
<@allstarschh>
have a nice weekend then