| 00:00 | <shu> | is there a null spec-internal value in HTML? |
| 00:01 | <shu> | i'd like a sentinel value for an internal field to mean "not present" in StructuredSerialize, and would like to avoid using JS undefined, as this value is never supposed to escape to script |
| 00:02 | <shu> | (i could also just make new [[Type]], with more branches) |
| 00:02 | <shu> | maybe that's preferable |
| 06:35 | <Noam Rosenthal> | annevk: I checked and destination for prefetch is empty (like regular fetch). I think this makes some sense. Prefetch is not a destination in itself - we don't know where the request is going to be end up. It's kind of like fetching the resource in a service worker |
| 10:30 | <annevk> | shu: I was wondering if that could be collapsed a bit more. It seems okay as-is, although the repetition irks me a bit. |
| 10:31 | <annevk> | Noam Rosenthal: yeah, though I'm not convinced we want to expose initiator in its current state |
| 10:32 | <annevk> | Noam Rosenthal: initiator just has a few values to match some known use cases, but it doesn't really have a design |
| 10:35 | <shu> | annevk: it irks me a bit too |
| 10:35 | <shu> | annevk: though it's like, extra explicit? and that seems like a plus |
| 11:12 | <Noam Rosenthal> | Noam Rosenthal: initiator just has a few values to match some known use cases, but it doesn't really have a design prefetch a a purpose, not the whole concept of initiator |
| 11:12 | <Noam Rosenthal> | annevk: mainly because having it as a header is a concept that's been around for a while and has a good use case |
| 11:18 | <Noam Rosenthal> | annevk: we can build on it later if we want to expand on the initiator concept, doesn't have to be all or nothing IMO |
| 11:27 | <annevk> | Noam Rosenthal: what is the use case? |
| 11:38 | <Noam Rosenthal> | annevk: it allows servers to opt-out of being prefetched, or to change their max-age so that a prefetched page doesn't expire, and also to not count prefetches towards "success rate" of loading a page |
| 11:38 | <Noam Rosenthal> | I think the latter is perhaps the most common use case |
| 11:49 | <Noam Rosenthal> | annevk: the latter is important for more than analytics... some web pages rely on "you visited this page last at..." for all sorts of things. without deferring between a prefetch and a regular document fetch, that kind of data gets messed up |
| 12:55 | <johannhof> | Does anyone know why I can suddenly no longer use [=origin=] or [=/origin=] to refer to the HTML origin concept in ReSpec? i.e. https://html.spec.whatwg.org/multipage/browsers.html#concept-origin |
| 12:55 | <johannhof> | The error message links to https://respec.org/xref/?term=origin&types=_CONCEPT_ where it does not seem to appear |
| 13:11 | <salty-horse> | Hi. Do you know of any efforts to standardize OpenGraph, by WHATWG or another group? |
| 13:44 | <freddy> | https://indieweb.org/The-Open-Graph-protocol seems to have some good material (albeit not a "neutral" source) |
| 14:05 | <salty-horse> | https://indieweb.org/The-Open-Graph-protocol seems to have some good material (albeit not a "neutral" source) |
| 14:22 | <Noam Rosenthal> | Not looking for material or documentation, but for ways to shape where it's going and things around it. https://ogp.me/ only leads to dead Facebook pages and google groups. A lot of the web treats it as a default but there's no guidance around it. I'm specifically wonder what it would mean to suggest that web server will support a "lightweight get" request that only returns enough data to render a preview of the page. But I have no idea who to talk to. |
| 14:23 | <salty-horse> | Probably facebook? |
| 14:25 | <Noam Rosenthal> | salty-horse: yea facebook likely created it and then deprioritized. you won't find much about this in standard bodies I'm guessing |
| 14:50 | <salty-horse> | funny how something most content-based websites use is abandoned |