| 15:01 | <annevk> | Domenic: https://twitter.com/brokencodebot/status/1044491810834448384 I noticed this too, but forgot to report it; known? |
| 15:01 | <annevk> | E.g., I'm not seeing an icon on https://dom.spec.whatwg.org/ |
| 15:10 | <Domenic> | annevk: ricea also noticed and filed on whatwg/streams. It's a service worker bug. I can fix now I Think. |
| 18:00 | <annevk> | cool |
| 21:30 | <MikeSmith> | TabAtkins: https://github.com/w3c/mdn-spec-links has data that can be used to generate MDN annotations for any given spec |
| 21:31 | <MikeSmith> | I just created it a few hours ago |
| 21:31 | <MikeSmith> | currently has data for 218 specs |
| 21:33 | <MikeSmith> | please lemme know if you think the JSON format of the files would work for the purposes of adding a new MDN-annotating feature to Bikeshed |
| 21:35 | <MikeSmith> | the data for each spec ID is an array of arrays with the MDN url fragment, MDN article title, and MDN article summary ーfor each MDN article that has a link to that spec ID |
| 21:36 | <MikeSmith> | could change the format to have "mdn_url", "mdn_title", and "mdn_summary" keys instead of just an array |
| 21:37 | <MikeSmith> | but that seems like overkill, and a bit wasteful, given the overall size of the collective data |
| 21:37 | <MikeSmith> | but still if you think it would work better to have keys there, I could easily change it to that |
| 21:38 | <MikeSmith> | also published/exposed at https://w3c.github.io/mdn-spec-links/ |
| 21:39 | <MikeSmith> | e.g., https://w3c.github.io/mdn-spec-links/css-logical-props.json |
| 21:40 | <MikeSmith> | and https://w3c.github.io/mdn-spec-links/SPECMAP.json maps each spec (base) URL to the corresponding *.json file for it |
| 21:47 | <domfarolino> | Domenic: Could you help me find where it is specified that a link should try and obtain resources whenever its `href` is changed? |
| 21:47 | <domfarolino> | For images, we have https://html.spec.whatwg.org/multipage/images.html#relevant-mutations, and I'm wondering if there is a corresponding dfn for links |
| 21:48 | <domfarolino> | s/that last link/https://html.spec.whatwg.org/multipage/images.html#when-to-obtain-images |
| 22:01 | <Domenic> | domfarolino: https://html.spec.whatwg.org/multipage/semantics.html#obtaining-a-resource-from-a-link-element |
| 22:02 | <Domenic> | with an override for rel=modulepreload, and in theory an override for rel=stylesheet per https://github.com/whatwg/html/issues/968 but that part of the spec is rather borked |
| 22:03 | <domfarolino> | Domenic: Ah, right but is it specified when those "obtain" algorithms should be called? For example it seems to be called whenever `href` is updated at the very least, and I'm wondering if that is spelled out somewhere |
| 22:05 | <Domenic> | It's per rel, e.g. https://html.spec.whatwg.org/multipage/links.html#link-type-stylesheet or https://html.spec.whatwg.org/multipage/links.html#link-type-modulepreload . (The latter seems like it should do more cross-linking... in general probably there should be a central definition for "appropriate times to obtain the resource" and then the individual rels should refer to that...) |
| 22:08 | <domfarolino> | Oh, wow, yep I totally missed those "appropriate times to..." sentences |
| 22:10 | <domfarolino> | Yeah a more centralized "appropriate times..." dfn would be nice I think |
| 22:13 | <Domenic> | PR welcome, if you want to shave that yak :) |
| 22:22 | <domfarolino> | I'm interested; will attempt after working on `imagesrcset` and `imagesizes` for link, and updating preload spec |
| 22:48 | <eeeps> | domfarolino: is there an issue about preloading imgsrcset and imgsizes? Can't find one. |
| 22:48 | <eeeps> | wait dang https://github.com/w3c/preload/issues/120 |
| 22:49 | <eeeps> | nm |