- From: Zamralik <notifications@github.com>
- Date: Mon, 27 Sep 2021 06:35:37 -0700
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <whatwg/fetch/issues/551/927881766@github.com>
> > > > So imagine if the fetch API added this capability to have a body with a GET request. It might not even work on some operating systems anyway, so browsers would be forced to not support it for the sake of consistency. > > This is not true, it's the other way around. > If The Fetch API added this capability, browsers and other frameworks would have to start supporting it eventually. Yes, it would be a somewhat painful time at first, but not more painful than it currently is now limiting peoples applications for arbitrary reasons. Exact ! What we can be certain of is that browsers, OS, proxies, ... will never bother implementing something that is explicitly forbidden by the standard. The way it works is : 1) Standard says something is fine 2) It is slowly implemented on some products 3) It's implemented enough that it become used with a polyfill/compatibility wrapper 4) As it is more and more used, it gets implemented on every products 5) It is used raw without a polyfill/compatibility wrapper Being allowed by the standard is the first step. The only reverse situation is when you have a step 0) => A nice missing feature that is not mentioned in the standard is added to some products But it will never happen if that feature is forbidden by the 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/fetch/issues/551#issuecomment-927881766
Received on Monday, 27 September 2021 13:35:50 UTC