Bug 33777
| Summary: | Iframe readyState is equal to "complete" when the Dom is still not ready. | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Grant Galitz <coolg1024> |
| Component: | Frames | Assignee: | Nobody <webkit-unassigned> |
| Status: | UNCONFIRMED | ||
| Severity: | Normal | CC: | ap, karlcow, webkit.org |
| Priority: | P3 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | All | ||
| OS: | All | ||
| See Also: | https://bugs.webkit.org/show_bug.cgi?id=17761 | ||
Grant Galitz
When a form targets an iframe, the iframe's readyState equals complete one millisecond too early. This is seen by the fact the Dom has a root element of HTML that has no children.
Though one millisecond later the Dom is mapped outand has children.
The iframe is an XML document.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Grant Galitz
ThIs breaks the iframe POST Ajax method
Xavier Morel
I guess this trunk revision was merged into Safari 5.1, because I now see this problem any time I try to get the result of an interaction uploading a file (e.g. via the jquery.forms plugin).
Alexey Proskuryakov
Does any standard specify readyState? If it's about network loading, then it seems reasonable that it can be complete before parsing is done.
Do you have a complete test case that you could attach to the bug?
Karl Dubost
> Returns "loading" while the Document is loading, "interactive" once it is finished parsing but still loading subresources, and "complete" once it has loaded.
https://html.spec.whatwg.org/multipage/dom.html#reporting-document-loading-status
This requires a test.
complete means all the subresources have been loaded.