| 00:44 | <atrigent> | hello! apologies if there's a better place to ask this, but I'm unsure about this: https://html.spec.whatwg.org/multipage/images.html#images-processing-model:concept-microsyntax-parse-error - what would the difference be between fatal and non-fatal in this context? |
| 03:29 | <MikeSmith> | atrigent: “non-fatal” in that context means that parsing does not fail. It means the parser doesn’t stop but continues on despite the error in the input. |
| 03:34 | <atrigent> | MikeSmith: so here: https://html.spec.whatwg.org/multipage/images.html#parsing-a-srcset-attribute:concept-microsyntax-parse-error for example, the commas would set there as having been a parse error, but otherwise they would basically just be ignored? |
| 03:40 | <MikeSmith> | atrigent: right |
| 03:40 | <atrigent> | ok, thank you |
| 03:41 | <MikeSmith> | if you look at https://html.spec.whatwg.org/multipage/images.html#image-candidate-string you see that the definition of “image candidate string” says whitespace is valid there but says nothing about commas |
| 03:42 | <MikeSmith> | but the parser is required to accept commas in there if an author makes a mistake and puts any in despite it not being valid |
| 03:42 | <atrigent> | well it does say "A valid non-empty URL that does not start or end with a U+002C COMMA character (,)" |
| 03:43 | <MikeSmith> | ah yeah OK |
| 03:45 | <atrigent> | but yeah, I guess the actual implementation is supposed to be a little more permissive |
| 03:46 | <MikeSmith> | anyway FWIW the HTML checker at https://validator.w3.org/nu/ will still report an error for those cases ー even though browsers will accept that input, the checker still reports it, since the checker’s purpose is to inform authors about cases that don’t match the spec requirements |
| 03:46 | <atrigent> | ok, interesting |
| 04:35 | <domfarolino> | Domenic: If I understand https://github.com/whatwg/html/issues/4267 correctly, https://null-referrer-script.glitch.me/ is a good demonstration of the path-dependence? |
| 04:35 | <domfarolino> | (I made it because I believe Chrome + Safari 12 behave as if all event handler fn's have null [[ScriptOrModule]], while FF seems OK) |
| 12:04 | <jgraham> | gsnedders: Not pteradactyl, but ptarmigan, c.f. https://en.wikipedia.org/wiki/Lagopus |
| 13:21 | <Ms2ger> | > The p- was added due to a mistaken belief in a Greek origin |
| 13:21 | <Ms2ger> | lol English |
| 14:03 | <annevk> | yoav: I don't think you want to use for=/ on a <dfn> |
| 14:03 | <Ms2ger> | That was probably my suggestion, sorry |
| 14:03 | <annevk> | yoav: not entirely sure if that is what's going amiss on https://travis-ci.org/whatwg/fetch/builds/481359853 though, but if it is, maybe ask Bikeshed for a better error message |
| 14:04 | <annevk> | yoav: either way, I've never used for=/ on a <dfn> so I'd ask for removal anyway 😃 |
| 14:05 | <yoav> | OK, how should I define a general concept, compared to one owned by a specific object type? |
| 14:05 | <yoav> | just remove the `for`? |
| 14:06 | <annevk> | yoav: yeah |
| 14:06 | <yoav> | will do! |
| 14:07 | <yoav> | Regarding "client-hints" vs. "client hints", I don't really care if it's one or the other |
| 14:07 | <annevk> | yoav: <dfn export>i am generic</dfn>; <dfn for=something>i am generic</dfn> holds a <a for=/>i am generic</a>; <a for=/>something</a>'s <a for=something>i am generic</a> is the best |
| 14:07 | <yoav> | I got the feeling you prefer "client hints" |
| 14:07 | <yoav> | should I switch to that? |
| 14:08 | <annevk> | yoav: I mostly want consistency, ideally grounded in something |
| 14:10 | <yoav> | "grounded in something" - is there some convention that indicates we should take one route over the next? |
| 14:10 | <annevk> | yoav: I'm not sure, I'm not a native speaker, so I guess I'd defer to the client hints RFC |
| 14:11 | <yoav> | OK |
| 14:12 | <annevk> | JakeA: you around? Why does cache.put clone the response? |
| 22:54 | <Bnaya> | Hey all :) |
| 22:55 | <Bnaya> | I was thinking today that im missing the ability to abort fetch response.json() and other async tasks |
| 22:57 | <Bnaya> | or the signal that was passed to the fetch() also controls all the async calls on the response obejct |