belCreateElement TypeError in Safari
See original GitHub issueRunning into an error with onload
and onunload
events in Safari. Can verify when removing the load attributes from the element the error is suppressed.
TypeError: Function.caller used to retrieve strict caller
Here is a temp URL: http://ec2-54-201-45-223.us-west-2.compute.amazonaws.com
Issue Analytics
- State:
- Created 7 years ago
- Comments:8 (3 by maintainers)
Top Results From Across the Web
Javascript ES6 TypeError in Safari & IE - Stack Overflow
It makes an Ajax call to show a data in DOM, which works for Chrome and Firefox but for some reason Safari gives...
Read more >Safari 11.0 typeError - Apple Community - Apple Discussions
Safari 11.0 typeError. I'm running Mac OS High Sierra version 10.13.1 (17B48) on MacBook Pro (Retina, 15-inch, Early 2013).
Read more >TypeError: undefined is not an object in Safari (MacOS and ...
The Cart overlay is failing to display sometimes in Safari on MacOS and iOS. It is very non-deterministic and I've not been able...
Read more >uppy - UNPKG
... $$selfFulfillment","TypeError","lib$es6$promise$$internal$$cannotReturnOwn" ... n * Falls back to prompt() when the easy way fails (hello, Safari!)\n ...
Read more >How to Fix TypeError: Null is Not an Object in JavaScript
This specific error message is shown only on Safari. Other browsers display a different message for this error. Error message: TypeError: null ...
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
Not sure if I should file a different bug for this, but on firefox, using choo I get this error
When using a view with onload, such as:
Using yo-yoify didn’t helped 😦
On further inspection, yo-yoify doesn’t fix the issue in safari. As far as I can see it occurs when having nested onload methods.