You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Expected result: No polyfills needed for current settings and browser
Actual result: A polyfill for fetch
Tested on Chrome version 117.0.5938.117, iOS 16.6, iPhone 11.
Furthermore, the polyfill is deficient in comparison to the native implementation. Specifically, the Response object that gets passed to its promises doesn’t have a body property (that should be a ReadableStream). This is causing problems for us downstream, as it causes NPEs in the ClojureScript SSE client we use that is based on fetch.
The text was updated successfully, but these errors were encountered:
Bug report
What
Requesting https://polyfill.io/v3/polyfill.js?features=fetch on Chrome iOS returns a polyfill for fetch, even though Chrome supports the fetch API natively.
Details
To reproduce:
Tested on Chrome version 117.0.5938.117, iOS 16.6, iPhone 11.
Furthermore, the polyfill is deficient in comparison to the native implementation. Specifically, the Response object that gets passed to its promises doesn’t have a
body
property (that should be aReadableStream
). This is causing problems for us downstream, as it causes NPEs in the ClojureScript SSE client we use that is based on fetch.The text was updated successfully, but these errors were encountered: