| 08:50 | <yhirano> | annevk: hi |
| 08:50 | <yhirano> | annevk: I have a question about https://bugs.chromium.org/p/chromium/issues/detail?id=757387 which is reported by you |
| 08:51 | <yhirano> | annevk: it seems https://github.com/web-platform-tests/wpt/blob/master/fetch/api/basic/scheme-data.any.js expects a non-empty body for HEAD and everyone passes the test. |
| 08:51 | <yhirano> | annevk: https://wpt.fyi/results/fetch/api/basic/scheme-data.any.html?label=master&label=experimental&aligned |
| 08:52 | <yhirano> | annevk: do you know the reason for the firefox behavior? |
| 09:01 | <annevk> | yhirano: if I had to guess it's because it ignores the method for data URLs |
| 09:02 | <annevk> | yhirano: I think we're okay with fixing that though |
| 09:03 | <yhirano> | annevk: So your opinion is null-ing the response body for HEAD requests is good for both xhr/fetch, right? |
| 09:06 | <annevk> | yhirano: yeah, making it depend on who provided the response seems weird |
| 09:07 | <annevk> | yhirano: I'd r+ a fix to that test; once that's done I'd be happy to help file bugs |
| 14:18 | <annevk> | If anyone needs a focus-related review from Mozilla, best to add smaug____ to the reviewer list. I've done it for some HTML PRs, but I might have missed some. (cc Domenic) |
| 14:18 | <smaug____> | ha, "thanks" :p |
| 14:19 | <smaug____> | (but yes, kick me if I'm slow with reviews) |
| 15:52 | <Domenic> | TabAtkins: there's no way to avoid a <dfn> (such as one used in an example) from showing up in "Terms defined by this specification", right? |
| 15:56 | <Ms2ger> | Domenic, please tell me if there is a way :) |
| 15:56 | annevk | raises hand for the newsletter |
| 16:00 | <Domenic> | In general "Terms defined by this specification" and its counterpart for "Terms defined in other specifications" feels a little unloved, e.g. my old issue about allowing us to preserve the casing on imported <dfn>s in the latter. Ah well. |