Re: [whatwg/encoding] Non-browser versus JavaScript (#87)

I guess the main problem here is the inconsistency across standards. URL for instance says nothing about its API.

Ideally I'd want all JavaScript environments to expose this and at a minimum it needs to be all browsers. Maybe we should just state something like that. And say that other programming languages are probably best to adopt an API that suits their needs best.

(And yes, I don't think we'd expand scope either way. Optional features make a poor standard.)

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