| 03:19 | <MikeSmith> | TabAtkins: was a change recently made in Bikeshed to replace the generated-ID pattern for constructor definitions? |
| 03:20 | <TabAtkins> | Not that I remember? What are you seeing? |
| 03:20 | <MikeSmith> | like, what as https://drafts.csswg.org/css-font-loading/#dom-fontface-fontface-family-source-descriptors-descriptors is now https://drafts.csswg.org/css-font-loading/#dom-fontface-constructor-family-source-descriptors-descriptors |
| 03:21 | <MikeSmith> | and was https://drafts.csswg.org/cssom-view/#dom-mediaquerylistevent-mediaquerylistevent-type-eventinitdict-eventinitdict is now https://drafts.csswg.org/cssom-view/#dom-mediaquerylistevent-constructor-type-eventinitdict-eventinitdict |
| 03:24 | <MikeSmith> | so far the only three specs which I have noticed that has happened for are css-font-loading, cssom-view, and resize-observer |
| 03:25 | <MikeSmith> | (and I ask because those links are gonna break if they are referenced elsewhere; e.g., MDN) |
| 03:29 | <MikeSmith> | (I’m running a script now to check if it did break any MDN links) |
| 03:29 | <TabAtkins> | Ah, hm, I guess switching to the constructor method syntax doesn't trigger the same codepath as the Constructor extended attribute. |
| 03:29 | <TabAtkins> | I'll fix |
| 03:36 | <MikeSmith> | TabAtkins: OK |
| 03:36 | <MikeSmith> | (my script is still running) |
| 03:43 | <TabAtkins> | Yeah a few more CSS specs will trigger it, since Brian fixed a few as well |
| 03:49 | <MikeSmith> | ok |
| 14:15 | <domfarolino> | annevk: Per-specI believe the following will lead to a double-fetch: 1) loading=lazy image is deferred 2) crossorigin attr on the image is changed 3) The image is scrolled into view. Do you agree? |
| 14:16 | <annevk> | domfarolino: well, it's not clear if the image was fetched to begin with if it was outside the viewport, but if it was, yes |
| 14:17 | <domfarolino> | annevk: I'm assuming it is outside the viewport, and not fetched |
| 14:17 | <annevk> | domfarolino: but then it'll be fetched with CORS and the image doesn't have CORS response headers so that'll fail |
| 14:18 | <annevk> | domfarolino: right? |
| 14:18 | <annevk> | domfarolino: anyway, gotta go |
| 14:20 | <domfarolino> | annevk: I'm just making sure it'd fetch twice, regardless of the server. |
| 14:20 | <domfarolino> | annevk: Would only one of the fetches fire load/error events? (yep, enjoy your weekend) |
| 14:26 | <annevk> | domfarolino: why would it fetch twice? Not sure about events |
| 14:29 | <annevk> | I’ll have time Monday; enjoy yours too! |
| 18:02 | <bathos> | Does anyone know offhand if there’s been discussion of bringing first class support for AbortController/AbortSignal to the Web Animations API? Google hasn’t turned anything up so far. |
| 19:50 | <TabAtkins> | bathos: Don't think there's been any movement in that direction, no. File an issue on w3c/csswg-drafts with some details? |
| 23:32 | <eeeps> | Just when I thought I'd made wattsi happy (builds locally!), the GitHub integration is yelling at me for a new reason https://github.com/whatwg/html/pull/5112 |
| 23:32 | <eeeps> | "💥 Error: EISDIR: illegal operation on a directory, read 💥" what does it mean? |