Re: [whatwg/url] Make URL's origin getter return null for file URLs (#506)

I'm very pessimistic about browsers getting there. The amount of anger we get any time file: URLs get less access to new features than the actual web is high (e.g. https://github.com/whatwg/html/issues/8121), and actively taking away the ability to `fetch()` other file: content seems unlikely to go well.

Anyway, I'm ambivalent the proposal at hand. I like the idea of getting at least surface-level interop. I think I would slightly prefer picking some other representative value (e.g. Chromium's "`file://`") for file URL origins, to represent "here be dragons", and leaving "`null`" for actually-opaque origins that have well-defined semantics.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/url/issues/506#issuecomment-1356182181
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/url/issues/506/1356182181@github.com>