- From: Paul Hawxby <notifications@github.com>
- Date: Thu, 03 Feb 2022 06:43:57 -0800
- To: whatwg/url <url@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 3 February 2022 14:44:13 UTC
> I think the main reason we have not made a lot of progress here is lack of browser-related use cases. Apart from browsers the API is only supported by Node.js. If I'm reading this right it sounds like @annevk justification for not wanting to make changes to the API is because it's not a problem in browsers, and who cares about Node. There has been more than enough people in this issue and [related Node issue](https://github.com/nodejs/node/issues/12682) saying this is a problem, whether you do or don't see the use case many other people do have perfectly valid use cases. I get why it may well be difficult or problematic, especially if it involves changing an active API but the initial implementation was short-sighted and missed a core piece of functionality people actually need. This needs a course correction. -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/url/issues/531#issuecomment-1029060206 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/url/issues/531/1029060206@github.com>
Received on Thursday, 3 February 2022 14:44:13 UTC