| 03:17 | <Domenic> | Yeah, there's a bug to clean that up one day |
| 03:17 | <Domenic> | https://github.com/whatwg/html/issues/1725 |
| 04:09 | <domfarolino> | annevk: So I guess we’re leaning towards removing “auto” for now (from lazy load), and therefore the “lazy loading mode” abstraction over the attr value, until we re-intro something with a controlling mechanism (i.e., document policy) for auto? |
| 05:27 | <annevk> | Mek: there’s an open issue to define top-level origin against HTML |
| 05:28 | <annevk> | Mek: with that we can define HTTP cache partitioning and such and also have a building block for requestStorageAccess() partitioning |
| 05:28 | <annevk> | domfarolino: yeah |
| 08:50 | <annevk> | Domenic: I guess what I wanted to say is that I think it would be weird if the two things same-site compared could not always be called sites |
| 09:58 | <littledan> | is anyone aware of ongoing work about passing fetch options to more places, e.g., permitting integrity for more things? There's been discussion of an out-of-band manifest for integrity, or URL changes for other sorts of reasons, but I don't know if there are detailed proposals |
| 10:00 | <littledan> | context: I'm looking into https://github.com/littledan/proposal-module-attributes/ and sort of wondering if there's something more general we should be doing for fetch options, given that those are a long-time need (and arguably higher priority than JSON modules themselves...) |
| 12:12 | <annevk> | littledan: https://github.com/whatwg/html/issues/4938 has some discussion and pointers to prior discussion |
| 12:41 | <littledan> | Fascinating, I had missed that. Thanks for the pointers. |
| 15:25 | <domfarolino> | littledan: Some older discussion at https://github.com/WICG/import-maps/issues/21 too it seems |