Open
Bug 1493878
Opened 7 years ago
Updated 1 year ago
iframe.contentDocument is changed across loading even when it has no src or srcdoc
Categories
(Core :: DOM: Core & HTML, defect, P2)
Core
DOM: Core & HTML
Tracking
()
People
(Reporter: xidorn, Unassigned)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
|
300 bytes,
text/html
|
Details |
See the attached testcase.
It shows that iframe.contentDocument is changed during the loading.
This behavior is different from both Chrome and Edge. It's not clear to me where piece of spec is related, but it's something not interoperable.
This difference causes some web-platform tests to fail in unexpected way, see for example some discussion in web-platform-tests/wpt#13102.
Also it doesn't seem to be useful that we create two different documents in the process.
Comment 1•7 years ago
|
||
There is the initial about:blank created if .contentDocument is accessed early, and then a new about:blank is loaded (because no src is treated as src=about:blank).
The usefulness comes from having consistent behavior.
Initial about:blank is created always if .contentDocument is accessed early enough, and then new page is just loaded. Not having two about:blanks means special casing about:blank.
hsivonen might recall some more details here regarding other implementations.
Comment 2•7 years ago
|
||
Per spec, there should be no about:blank load in the
> Otherwise, if the element has no src attribute specified, and the user agent is processing the iframe's attributes for the "first time"
case. I'm pretty sure we have existing bugs on the fact that we do have such a load... Fixing this would be a pretty good idea, i think.
Updated•7 years ago
|
Priority: -- → P3
Updated•6 years ago
|
Type: enhancement → defect
Priority: P3 → P2
Updated•6 years ago
|
Webcompat Priority: ? → P2
Comment 5•6 years ago
|
||
(Lowering webcompat priority because Google fixed the GCP console bug on their end)
Webcompat Priority: P2 → P3
Comment 6•5 years ago
|
||
This appears to have hit GCP a second time in a slightly different way, as seen in https://webcompat.com/issues/57957
See Also: → https://webcompat.com/issues/57957
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•