If something in the iframe is actually messing with behavior of the parent document, that’s a violation of cross-origin protections and a bug in the browser. FWIW I still can’t reproduce it on Chrome 64.
If something in the iframe is actually messing with behavior of the parent document, that’s a violation of cross-origin protections and a bug in the browser. FWIW I still can’t reproduce it on Chrome 64.