| 00:58 | <dandclark> | Hi annevk , I'd appreciate your thoughts on my comments in the writingsuggestions PR: https://github.com/whatwg/html/pull/10018#issuecomment-1960295747 I think this is the last thing before this PR can move forward, so hoping to settle on an approach and get this resolved. |
| 16:39 | <Dominic Farolino> | Does anyone know if https://html.spec.whatwg.org/C#pragma-directives:attr-meta-http-equiv-keyword-default-style is supposed to re-apply a new style sheet right then and there (and therefore have script-observable changes)? |
| 16:40 | <Dominic Farolino> | I ask because https://drafts.csswg.org/cssom/#change-the-preferred-css-style-sheet-set-name seems to be incredibly vague. It just "enables" a style sheet, which flips some internal flags/state, but I'm not sure if that's supposed to impact the actual live rendering/styles. |
| 16:42 | <Dominic Farolino> | Noam Rosenthal: |
| 16:51 | <Dominic Farolino> | Interestingly in Chrome, we only process it after all pending DOM mutations are complete: https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/renderer/core/html/html_meta_element.cc;l=582;drc=8e98d0b38a95fc7fd4fc51cd59be77c5bf9e315c |
| 17:16 | <Noam Rosenthal> | Dominic Farolino: there's nothing that defers it behind a task/microtask so seems like it, but perhaps others have more context |
| 18:37 | <Dominic Farolino> | Oh, I didn't mean scheduling-wise. I just didn't know if https://drafts.csswg.org/cssom/#change-the-preferred-css-style-sheet-set-name was actually supposed to have script-observable consequences to styles? It seems to deal exclusively in internal bit flipping and flag setting, and I'm unclear if that stuff is supposed to result in observable changes to the document's styles. |
| 18:38 | <Dominic Farolino> | I guess it is... idk I've always hard a hard time evaluating when real observable changes are supposed to take place in CSS specs. They seem very disconnected from HTML Standard in that sense |
| 18:49 | <tech-enthusiastic> | Is this the correct place to give an idea of a Web API that generates PDF files? |
| 19:14 | <tech-enthusiastic> | var pdf = new PDF(); //Function to create pages //Function to create pages in array, can also be used to delete a page or modify its content //Function to delete pages //File output functions |
| 19:37 | <akaster> | Domenic: in https://github.com/whatwg/html/issues/9920#issuecomment-1804977146 you told me that: Despite "object" in the name, "environment settings objects" are not JS objects. You can pass them anywhere. Which... still doesn't make sense to me :). The only place that we create the ESO is when attaching it to a Realm as its [[Host Defined]] slot. So in my mental model, the HTML concept of Environment Settings Object is very much tied to the Realm it was created for. It also holds two weak sets for module resolution. And there's always a 1-1-1 mapping between a realm, a global object, and an environment settings object, per https://html.spec.whatwg.org/multipage/webappapis.html#realms-settings-objects-global-objects So I don't see how always using an environment settings object from a different realm (the Worker's owner's realm) as a Fetch Request's client can possibly work in a case where I implement Workers in a new process. |
| 19:43 | <akaster> | I'm not entirely sure what fields/algorithms from the environment settings object "fetch a classic worker script" and "fetch a module script graph" need, but I'm hoping it's only like, the origin and url and other easily serializable data? But Fetch Request explicitly says that its client must be an environment settings object or null |