Google Chrome Won't Accept .contentDocument or .contentWindow

前端 未结 3 483
隐瞒了意图╮
隐瞒了意图╮ 2021-01-06 19:06

When I try my code out:

Testing.html -



        
相关标签:
3条回答
  • 2021-01-06 19:45

    I've noticed that both the contentDocument and getSVGDocument (for svg objects from svg files) will work fine if the code is from a web server, but when I copy the code to a local file, it will not work.

    Here's a sample link with a code I coppied from which works on the web but not from my disk.

    Here's the solution I just found from Chrome (thanks to Artem S), i.e. using the --allow-file-access-from-files flag.

    0 讨论(0)
  • Try it without the .document

    var form = iframeEl.contentDocument.getElementById('hi').getAttribute('href');
    

    instead of

    var form = iframeEl.contentDocument.document.getElementById('hi').getAttribute('href');
    
    0 讨论(0)
  • 2021-01-06 19:54

    The answer from @IsraelGav is correct in the sense that this problem occurs when the code is accessed from a local file but not when accessed from a web server. It is also correct in the sense that using the --allow-file-access-from-files flag can allow the local file to be accessed by Chrome.

    However, it misses an important security concern here. Both the concern, as well as an alternative possible solution, were originally described in this other SO answer by @orszaczky. To summarize the alternative solution: On Windows, install http-server (npm install -g http-server) and run http-server from your project directory. On Mac/Linux, run python -m SimpleHttpServer from your local directory. You can now access the locally hosted web site in your browser. On Windows I had to use localhost:8080 while on the Mac I had to use localhost:8000.

    By the way, this is not only an issue for Chrome (v49.0) but also for Opera (v35.0), on both Windows and Mac.

    0 讨论(0)
提交回复
热议问题