Chrome actually supports iframe.contentWindow.document , but there are some wrinkles that you probably fell victim to: if the file set to the iframe.src property is accessed locally (ie using the file "file: //" protocol), This property is not available in Chrome. This will happen if you specify the relative address of the file and try to test the script without using a web server such as IIS or Apache (just double-clicking it). The same goes for iframe.contentDocument .
I had a similar problem where, for some odd reason, Chrome did not accept event handlers dynamically associated with iframes. Then I found the note in this article tested using Apache, and unfortunately it started working.
Jurij belous
source share