| 05:32 | <MikeSmith> | https://developer.apple.com/safari/technology-preview/release-notes/ |
| 05:32 | <MikeSmith> | > Implemented imagesrcset and imagesizes attributes on link rel=preload |
| 15:19 | <annevk> | TimothyGu: oooh explicit state for initial about:blank is great |
| 16:47 | <MikeSmith> | annevk: so by the way https://stackoverflow.com/questions/56575716/content-security-policy-inside-iframe-affects-whole-page-on-firefox did turn out to be a bug in Firefox 68 and earlier, maybe due to regression caused by some refactoring, I dunno |
| 16:47 | <MikeSmith> | but anyway fixed in Firefox 69 |
| 16:48 | <MikeSmith> | KWierso used mozregression to isolate it |
| 16:48 | <MikeSmith> | well, to identify the patch which fixed it |
| 16:50 | <Domenic> | annevk or anyone: is there any prevention for fetches from inactive documents? E.g. `inactiveIframe.eval('fetch("https://example.com/")')` |
| 17:04 | <annevk> | Domenic: it's an open issue (as is canceling when documents become inactive) |
| 17:05 | <annevk> | MikeSmith: ah cool, thanks for the update (I did not get to it, evidently) |
| 17:05 | <Domenic> | I recall canceling when documents become inactive being vaguely defined, if not fully hooked up. |
| 17:08 | <annevk> | Domenic: true, but it's unclear to me if the specific timing is interoperable across implementations, based on bugs I've seen come by but not have prioritized |
| 17:08 | <Domenic> | Yeah, I was just unclear whether there was an intention of preventing future fetches or just canceling ongoing ones. |
| 17:09 | <annevk> | Domenic: there probably ought to be a prevention as well as the user has no way to deal with inactive documents |
| 17:09 | <annevk> | Domenic: otherwise they could likely be used to load resources the user has no control over |
| 17:11 | <annevk> | Reading more whatwg/html backlog and it seems TimothyGu has been touching many interesting bits recently |
| 17:12 | <annevk> | Looking forward to being able to catch up with all of that |
| 17:33 | <Domenic> | Yeah I think we just need someone to write WPTs for him :) |
| 20:05 | <innovati> | Just a historical curiosity - why is <div> named DIV, rather than something like <box> which seems self-explanatory and is just as short? |
| 20:06 | <innovati> | was there precedent for <div> in markup languages before HTML? |
| 20:47 | <astearns> | innovati: looks like it was only added in HTML3 (though HTML2 uses it in an example: https://tools.ietf.org/html/rfc1866 ) |
| 21:06 | <innovati> | astearns am I reading that correct that in the HTML2 example <div> is given as an example of an unsupported made-up tag? |
| 21:06 | <astearns> | that was my reading, too |
| 21:06 | <innovati> | thanks for finding this :D HTML history is so interesting |