Array.prototype.includes() not supported by IE
See original GitHub issueWhen visiting beta through IE, the site is unusable. There are two instances of includes
in the code base outside of the gulp file, and two solutions for fixing this.
- Add a polyfill for
Array.prototype.includes()
or - Refactor to remove
Array.prototype.includes()
Issue Analytics
- State:
- Created 7 years ago
- Comments:18 (9 by maintainers)
Top Results From Across the Web
includes() not working in Internet Explorer - javascript
String.prototype.includes is, as you write, not supported in Internet Explorer (or Opera). Instead you can use String.prototype.indexOf .
Read more >Cross Browser Compatibility of Array.prototype.includes in ...
Array.prototype.includes is Not Supported on Internet Explorer 11. If you use Array.prototype.includes and your users are using Internet ...
Read more >Conflict with IE11 due to usage of Array.prototype.includes()
Problem/Motivation. The matchCookieValue function doesn't work in IE11 , due to use of Array.prototype.includes():
Read more >Array.Includes is not supported on IE11 · Issue #27 - GitHub
Successfully merging a pull request may close this issue. fix(convert function): "Array.prototype.includes" throwing in IE kentcdodds/rtl-css-js.
Read more >Array.prototype.includes | Can I use... Support ... - CanIUse
Determines whether or not an array includes the given value, returning a boolean value (unlike indexOf ). Usage % of. all users, all...
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 FreeTop 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
Top GitHub Comments
@Bouncey This may be thinking a bit too far down the line, but I’ve been aware of this for some time since @bonham000 and I ran into this issue when we were developing the React curriculum. Several of those challenges err… include
includes()
😄So I guess my point is, maybe a polyfill is the best solution?
@BerkeleyTrue I can work on refactoring this.