New issue
Advanced search Search tips

Issue 875354 link

Starred by 4 users

Issue metadata

Status: Duplicate
Merged: issue 569511
Owner: ----
Closed: Aug 23
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Android , Windows , Chrome , Mac , Fuchsia
Pri: 2
Type: Bug



Sign in to add a comment

iframe load event should be fired asynchronously for initial about:blank page

Project Member Reported by timothygu@chromium.org, Aug 17

Issue description

Chrome Version: 70.0.3525.0 (Official Build) canary (64-bit)
OS: (e.g. Win10, MacOS 10.12, etc...)

What steps will reproduce the problem?

<body>
<script>
const frame = document.createElement('iframe');
let sync = true;
frame.onload = () => {
  alert(sync);
};
document.body.appendBody(frame);
sync = false;
</script>

What is the expected result?

"false" is alerted, like as it is in Firefox and Edge.

What happens instead?

"true" is alerted.

Please use labels and text to provide additional information.

If this is a regression (i.e., worked before), please consider using the
bisect tool (https://www.chromium.org/developers/bisect-builds-py) to help
us identify the root cause and more rapidly triage the issue.

For graphics-related bugs, please copy/paste the contents of the about:gpu
page at the end of this report.


 
For additional context, in the HTML Standard, the "completed loaded" flag is set asynchronously (https://html.spec.whatwg.org/multipage/parsing.html#completely-loaded), which has one of its reactions firing load event at the iframe element (https://html.spec.whatwg.org/multipage/iframe-embed-object.html#the-iframe-element:completely-loaded-2).

I tested this on macOS 10.13.6.
Mergedinto: 569511
Status: Duplicate (was: Untriaged)

Sign in to add a comment