this.contentDocument is null for safari mobile safari
See original GitHub issueI am having this error for safari/mobile safari
TypeError: null is not an object (evaluating 'this.contentDocument.defaultView')
I will keep debugging
Issue Analytics
- State:
- Created 7 years ago
- Reactions:7
- Comments:6 (1 by maintainers)
Top Results From Across the Web
Why is iframe.contentWindow == null? - Stack Overflow
I had this problem last week while playing with iframes (building an rtf editor), and yeah it's not ready yet.
Read more >HTMLIFrameElement.contentDocument - Web APIs | MDN
If the iframe and the iframe's parent document are Same Origin, returns a Document (that is, the active document in the inline frame's ......
Read more >IFRAME contentWindow is null - David Walsh Blog
When I first tried this method, I got a lame error about an IFRAME element's contentWindow property being null . Ugh. It didn't...
Read more >WebKit DOM Programming Topics: Cross-Document Messaging
Describes how to use JavaScript in web content and WebKit-based applications.
Read more >HTML | DOM IFrame contentDocument Property
The IFrame contentDocument property in HTML DOM is used to return the document object ... Opera 12.1 and above; Safari 3.0 and above....
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
Had the same issue in Chrome 57 on Mac OS, in a React JS project.
Error occurred when calling
unbind
incomponentWillUnmount
- notably though this only occurred after switching my project from React 15.3.1 to Inferno 1.6.2. It seems to be an issue with either my code or Inferno in my case - by the timeunbind
is being called the element has been removed from the DOM.For me it’s specifically this line from
unbind
that is breaking:I’m not sure if this is something that should be handled by the
unbind
function, but hopefully this information will be useful for any other devs encountering this problem.No, seems like #28 does not help. Tried to use version from the master. But it still fails with error
Cannot read property 'defaultView' of null
in lineelement.__resizeTrigger__.contentDocument.defaultView.removeEventListener
in unbind.