Summary: | parser does not create nodes inside <iframe> (test 4 in Acid3 'ignoring whitespace during NodeIterator walk' fails) | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Eric Seidel (no email) <eric> | ||||||||
Component: | New Bugs | Assignee: | Dave Hyatt <hyatt> | ||||||||
Status: | RESOLVED FIXED | ||||||||||
Severity: | Normal | CC: | darin, hyatt, ian | ||||||||
Priority: | P2 | Keywords: | HasReduction | ||||||||
Version: | 528+ (Nightly build) | ||||||||||
Hardware: | All | ||||||||||
OS: | All | ||||||||||
Bug Depends on: | |||||||||||
Bug Blocks: | 17064 | ||||||||||
Attachments: |
|
Description
Eric Seidel (no email)
2008-02-09 01:34:39 PST
Created attachment 19015 [details]
possible test case? (FF and Opera fail too)
I added Hixie to the CC list because I thought this was a bug in the test. But I'm not so sure now. I'll investigate this some soon. The failure remaining seems to have nothing to do with NodeIterator. The problem is that this is an <iframe> with a src that fails to load. At some point, when the load fails, presumably we are supported to fall back and display the fallback content instead as we do with <object>. I don't know what the test does to ensure that it doesn't try to run *before* the <iframe> has tried and failed to load its src, but I'm presuming it does something. If it doesn't then there could be an Acid3 bug. Then we have to make sure that the error from the server is treated as a failure. And make sure we do fallback. As far as I can tell we don't even try to do fallback for <iframe>. In fact, until now I had been under the impression that <iframe> was supposed to fall back only for browsers that don't support <iframe>, not for missing resources. This is news to me. I had no idea <iframe> was supposed to do this. Are you sure this isn't just a bug where the fallback content is always supposed to be present in the DOM? Created attachment 19046 [details]
Remove the special skipMode behavior for iframes.
Comment on attachment 19046 [details]
Remove the special skipMode behavior for iframes.
Never mind. It's more complicated than this. We need to enter a special "CDATA parsing mode" according to HTML5. What is inside the <iframe> should be treated as simple text.
Created attachment 19047 [details]
Treat <iframe> like <title> and <textarea>, since that's what it is really supposed to be like.
|