Bug 13636
| Summary: | <OBJECT> tags seem mistakenly included in the document's applet collection | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Brady Eidson <beidson> |
| Component: | Page Loading | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED FIXED | ||
| Severity: | Normal | Keywords: | InRadar |
| Priority: | P2 | ||
| Version: | 523.x (Safari 3) | ||
| Hardware: | Mac | ||
| OS: | OS X 10.4 | ||
| URL: | http://homestarrunner.com | ||
| Bug Depends on: | |||
| Bug Blocks: | 13634 | ||
Brady Eidson
Both in Safari 2.0 and ToT, it seems OBJECT tags were incorrectly included in a page's applet collection. This prevented (and continues to prevent) back/forward caching of certain pages.
Visit the above url in Safari/ToT WebKit and in Firefox
run "javascript:alert(document.applets[0].outerHTML);" from the location field
Firefox has 0, Safari/ToT have 1 - view the page source to see the big glaring OBJECT
Since Firefox correctly reports 0, it's hard to believe we ever did this for compatibility with FFX - however, I have not tried WinIE
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Brady Eidson
Correction - since FFX doesn't support outerhtml, amend the javascript to be "javascript:alert(document.applets[0]);"
It gives you back an undefined collection, whereas Safari hands back a collection (with 1 member)
Brady Eidson
ummm check that - I meant a null ELEMENT, and Safari gives back an HTMLObjectElement
Brady Eidson
http://trac.webkit.org/projects/webkit/changeset/12250 might be of interest
Brady Eidson
<rdar://problem/5190816>
Brady Eidson
Landed in r21359
Eric Seidel (no email)
Here is a link to the change:
http://trac.webkit.org/projects/webkit/changeset/21359