| 08:37 | <annevk> | wanderview: JakeA: small update: I added a certificate to macOS and found Chrome fails the test, but Safari passes |
| 08:40 | <annevk> | I guess Safari implements Fetch far more properly |
| 09:47 | <gsnedders> | FWIW: My birthday is next Friday; I'm in SF. If anyone wants to be part of something somewhere, ping me. |
| 16:19 | <wanderview> | annevk: isn't this something that webkit implemented early while we were still discussing? |
| 16:19 | <wanderview> | or am I thinking of something else and this should have been implemented this way from the start? |
| 16:21 | <annevk> | wanderview: a lot of this was set up this way upfront, but opaque redirects did come later; and I actually have not checked all details in Fetch again so should prolly keep quiet |
| 16:34 | <annevk> | wanderview: yeah so my comment about Safari doesn't make any sense |
| 16:35 | <annevk> | wanderview: they basically impl the change proposed in https://github.com/whatwg/fetch/pull/633 (where an opaqueredirect isn't parsed again) |
| 16:36 | <wanderview> | annevk: ah, ok |
| 20:33 | <yuhong> | So I assume that the HTML5 buzzword made more sense when things like IE6 was common, right? |
| 20:34 | <yuhong> | Of course, I do agree that it was probably a poor fit as a W3C standard from the beginning. |
| 20:34 | <yuhong> | Hence the web developer edition compromise. |