| 00:06 | <KiChjang> | does anyone know of a list of non-spec compliant features in mobile safari? |
| 00:06 | <KiChjang> | i'm particularly interested in XHR |
| 00:40 | <a-ja> | KiChjang, perhaps implementing Feature-Policy: sync-xhr ? |
| 00:40 | <KiChjang> | and fetch? |
| 00:40 | <KiChjang> | wait, is that CSP? |
| 00:40 | <a-ja> | that would affect fetch |
| 00:41 | <a-ja> | FP is newish |
| 00:42 | <a-ja> | WebAuthn API |
| 00:42 | <KiChjang> | hmm... that doesn't seem to be something i'm interested in knowing |
| 04:25 | <annevk> | TimothyGu: sorry, I won't get to event handlers this week |
| 04:26 | <annevk> | TimothyGu: forgot about a public holiday |
| 14:44 | <TimothyGu> | annevk: No problem |
| 23:14 | <jyasskin> | In https://fetch.spec.whatwg.org/#concept-main-fetch, I see "6. If the recursive flag is set, return response." IIUC, the recursive flag is set for any non-navigation redirect, so none of those will do things like set the response's url list. Is that right? |
| 23:21 | <Mek> | where would the recursive flag be set? "fetch" (i.e. https://fetch.spec.whatwg.org/#concept-fetch) seems to always call main fetch witohut the flag set |
| 23:22 | <Mek> | actually, that is what you said, never mind |
| 23:23 | <Mek> | either way it seems like the outer main fetch would still eventually do all those further steps? |
| 23:24 | <jyasskin> | Mek: Yeah, I think you're right. |
| 23:25 | <jyasskin> | Thanks. |