Bug 18664 - It seems that the "empty" step should run even if the UA is not processing the iframes' attributes for the first time
Summary: It seems that the "empty" step should run even if the UA is not processing th...
Status: RESOLVED FIXED
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks: 17075
  Show dependency treegraph
 
Reported: 2012-08-23 13:34 UTC by contributor
Modified: 2012-09-19 22:02 UTC (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description contributor 2012-08-23 13:34:16 UTC
Specification: http://www.whatwg.org/specs/web-apps/current-work/
Multipage: http://www.whatwg.org/C#process-the-iframe-attributes
Complete: http://www.whatwg.org/c#process-the-iframe-attributes

Comment:
It seems that the "empty" step should run even if the UA is not processing the
iframes' attributes for the first time; see
http://software.hixie.ch/utilities/js/live-dom-viewer/saved/1711

Posted from: 2001:4c28:a030:30:c15f:2afb:ede8:7db0
User agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:17.0) Gecko/17.0 Firefox/17.0
Comment 1 Ian 'Hixie' Hickson 2012-09-19 20:03:44 UTC
That test shows that the step _shouldn't_ run, actually, but that we should navigate to about:blank with replacement enabled.

Consider e.g.
   http://software.hixie.ch/utilities/js/live-dom-viewer/saved/1786
   http://software.hixie.ch/utilities/js/live-dom-viewer/saved/1787
Comment 3 Ian 'Hixie' Hickson 2012-09-19 20:13:10 UTC
   http://software.hixie.ch/utilities/js/live-dom-viewer/saved/1791

Looks like it should be "with replacement enabled" if the page has not "completely loaded", much as for form submission or the location.href setter.
Comment 4 contributor 2012-09-19 22:02:15 UTC
Checked in as WHATWG revision r7378.
Check-in comment: Attempt to make <iframe> loading more closely match reality. See tests in bug.
http://html5.org/tools/web-apps-tracker?from=7377&to=7378