Allow forcing polyfill
See original GitHub issueI found a bug in Chrome that window.fetch does not send cookie when POSTing, even have credentials set (see Issue 490519). So we may have to polyfill chrome as well, at least provide a way to do so.
Currently github/fetch only polyfills UA whose window.fetch is undefined. So it will not polyfill the broken fetch in chrome.
Issue Analytics
- State:
 - Created 8 years ago
 - Comments:9 (2 by maintainers)
 
Top Results From Across the Web
How to force Polymer to use polyfill - Stack Overflow
Polymer.dom = 'shadow' forces Polymer to use the shadow DOM by default (either the polyfilled one if you used webcomponents.js or natively ...
Read more >Polyfill JavaScript Only When You Need To - CSS-Tricks
The problem is that we're forcing modern browsers to run the old code when they don't have to. They support ES6, so can't...
Read more >Loading Polyfills Only When Needed - Philip Walton
The solution to this problem is to only load polyfills when they're needed, but as it turns out, in practice that's a lot...
Read more >How to use polyfills in your React app - LogRocket Blog
A polyfill allows you to use features that are not supported by a ... This will force the CDN to return the polyfill,...
Read more >Polyfills - Polymer Project
This small polyfill allows you to run compiled, ES5 elements on browsers that ... The webcomponents-lite.js file also supports forcing the polyfills on...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

I mean, that’s just not true. We have many examples, including production websites, getting credentials in Chrome. I asked you for a runnable repro case in the Chromium bug and you haven’t provided. I was going to wait until you did so but at this point you’re just spreading false information.
@tjwudi I just tried in Chrome 43.0.2357.65. Both
same-originandincludevalues forcredentials:key enable sending the cookie value. I’m sorry, but I can’t reproduce what you’re describing. And in your Chromium bug report, you tried to demonstrate the bug by including sample code, but then you said that thefetch()in the code isn’t native fetch, but your own wrapper that edits the option. You’ll have to provide complete code to demonstrate this issue.