| 09:02 | <GPHemsley> | Domenic: Does jsdom/url not fail tests with file:// bases and windows drive letters since the spec change? I'm trying to track down where/whether I'm going wrong... |
| 10:42 | <GPHemsley> | Domenic: Nevermind, I am indeed an idiot. |
| 17:05 | <benjamingr_> | Hey, I can't figure out why `e.total` gets set on a ProgressEvent HEAD request - I'm looking at https://xhr.spec.whatwg.org/#interface-progressevent |
| 17:37 | <annevk> | benjamingr_: https://github.com/whatwg/fetch/issues/284 |
| 17:37 | <annevk> | benjamingr_: tl;dr; bug |
| 17:39 | <benjamingr_> | Thanks |
| 17:42 | <benjamingr_> | FWIW, I think it's useful and I like the Chrome behavior better :D |
| 17:43 | <benjamingr_> | It enables you to see the content-length of things that are behind CORS and doesn't expose the header directly - I can use it in order to use HEAD to get the content length of CORS content and make decisions about how/if I want to download it - for example I can HEAD a resource and only download it if it's smaller than X bytes in a way that benefits the user. |
| 17:44 | <annevk> | benjamingr_: that's an argument for safelisting Content-Length, if indeed all user agents already leak it that way |
| 17:45 | <annevk> | benjamingr_: could you file an issue since it seems like something that should be fixed either way |
| 17:45 | <annevk> | benjamingr_: or at least something folks should be aware of |
| 17:45 | <benjamingr_> | Sure, do I file it against `fetch`? |
| 17:46 | <annevk> | benjamingr_: yeah |
| 17:46 | <benjamingr_> | Thanks, as always you've been a great help :) |
| 17:52 | <benjamingr_> | https://github.com/whatwg/fetch/issues/622 Thanks again annevk |
| 18:10 | <annevk> | 👍 |