Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Latest version 1.11.0 doesn't work on IE11
See original GitHub issueReports error:
SCRIPT5009: 'Proxy' is undefined
But old version (e.g. 1.7.2) has no such problem
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Billboard.js 1.11.0 doesn't support IE 11 · Issue #1145 - GitHub
Description Billboard.js v1.11.0 doesn't work in IE. I think that it's because It depends on d3-array 2.4.0 that doesn't support IE anymore.
Read more >jQuery not working with IE 11 - Stack Overflow
In my case, it started working when I went back to an older version of jquery. with jquery 2.2.3 it would show '$...
Read more >Run the latest version of Internet Explorer 11 - Microsoft Support
To be sure you have the latest version of Internet Explorer 11, select the Start button, select Settings > Update & security >...
Read more >Newer Chrome versions and IE11/Edge cannot drag and drop ...
Original report I found that the file 'misc/tabledrag.js' has been changed so that table dragging works on mobile devices.
Read more >Internet Explorer Still Does Not Go Away Today - Adrian Roselli
…Internet Explorer 11 desktop application will be retired and go out of support on June 15, 2022, for certain versions of Windows 10....
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
Hi @freewind
I’ve just put in a
try {} catch {}around the creation of the Proxy, so that for older environments it will just ignore it completely. You just won’t get as clear an error message if you misuse some parts of Async Actions, but you shouldn’t run into those issues if you are using it correctly in the first place 😉Hope that helps. Try out
1.11.2Thansk for the repo, by the way. I did test out the new version using that, and it all seemed to work fine.
Thanks so much for the quick response and new release!