| 07:56 | <annevk> | hsivonen: FWIW, I kinda think we should reopen the ISO-2022-JP issue to get answers at least at this point |
| 08:00 | <hsivonen> | annevk: ok |
| 09:16 | <annevk> | Oooh nice, GitHub records force pushes now |
| 14:24 | <Ms2ger> | annevk, will try to remember, but the label is certainly safer :) |
| 14:31 | <wanderview> | hmm... it seems you can't load a blob URL with query params appended in chrome or edge... is that supposed to work? |
| 14:49 | <annevk> | wanderview: per step 4 of https://url.spec.whatwg.org/#concept-url-parser, yes |
| 14:50 | <wanderview> | hmm, ok |
| 14:54 | <wanderview> | annevk: thanks... and here is the context of the question in case your curious: https://bugs.chromium.org/p/chromium/issues/detail?id=907452 |
| 14:55 | <annevk> | Ah, not due to a wpt failure |
| 16:14 | <annevk> | Domenic: I noticed in Firefox's code that there's also special handling for U+0000 when it comes to these popups |
| 16:14 | <annevk> | alert() et al |
| 16:24 | <Domenic> | annevk: https://github.com/whatwg/html/issues/4109 |
| 16:26 | <annevk> | ta |
| 17:11 | <Mek> | wanderview/annevk: blob URLs with query parameters are actually not supposed to work, I just somehow never followed up on https://github.com/whatwg/url/pull/371 (i..e the URL spec bits of sorting out the blob URL mess) when I was working on clarifying this last year... |
| 17:25 | <annevk> | Mek: why not? |
| 17:26 | <annevk> | Anyway, I guess better discussed in an issue |
| 17:26 | <Mek> | I don't remember if there was more than "three out of four browsers agree" when I was fixing the specs last year |
| 17:28 | <Mek> | also the FileAPI spec has always had the chrome/webkit/edge behavior, at some point it just was made non-normative when URL spec was written in an incompatible way. |
| 18:06 | <annevk> | I’d like to at least blame this to see if I considered this and had a reason |