Security DCHECK in <object> showing fallback content. |
|||
Issue description
Chrome Version: 69.0.3450.0 (Developer Build) (64-bit)
What steps will reproduce the problem?
(1) On a local server, navigate a 'dcheck-always-on' chrome to:
http://127.0.0.1:80/page1.html
where:
page1.html:
<object src="foo"> <b> Fallback </b> </object>
<script>
window.setTimeout(crashIt, 1000);
function crashIt() {
document.querySelector("object").contentDocument.defaultView.location.href = "https://127.0.0.2:80/page2.html";
page2.html:
<script>
window.setTimeout( () => window.location.href = "http://127.0.0.1:80/something.html", 1000);
</script>
(2) Wait for crash.
This goes back to an <object> with fallback content ending up with a frame. It probably shouldn't.
,
Jun 6 2018
Chrome Version: 69.0.3450.0 (Developer Build) (64-bit)
What steps will reproduce the problem?
(0) Use site-per-process.
(1) On a local server, navigate a 'dcheck-always-on' chrome to:
http://127.0.0.1:80/page1.html
where:
page1.html:
<object src="foo"> <b> Fallback </b> </object>
<script>
window.setTimeout(crashIt, 1000);
function crashIt() {
document.querySelector("object").contentDocument.defaultView.location.href = "https://127.0.0.2:80/page2.html";
page2.html:
<script>
window.setTimeout( () => window.location.href = "http://127.0.0.1:80/something.html", 1000);
</script>
(2) Wait for crash.
This goes back to an <object> with fallback content ending up with a frame. It probably shouldn't.
,
Aug 2
|
|||
►
Sign in to add a comment |
|||
Comment 1 by ekaramad@chromium.org
, Jun 6 2018