Summary: | <object> content breaks when file is forced to be downloaded | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Alex Haan <alex.haan> | ||||||
Component: | Frames | Assignee: | Nobody <webkit-unassigned> | ||||||
Status: | UNCONFIRMED --- | ||||||||
Severity: | Normal | CC: | aestes, ap | ||||||
Priority: | P2 | ||||||||
Version: | 528+ (Nightly build) | ||||||||
Hardware: | Mac (Intel) | ||||||||
OS: | OS X 10.7 | ||||||||
URL: | http://armeagle.nl/wdft/ | ||||||||
Attachments: |
|
Description
Alex Haan
2012-01-06 04:41:53 PST
Created attachment 121426 [details]
Test case file
> the frame is then malformed
What I see in Safari is that fallback content is displayed.
This is quite an edge case. I'm not even sure how to tell if it's a bug or correct behavior.
Can you just use iframe in all browsers? That's way more interoperable than object.
The past years objects have slowly turned into the replacement for iframes. This of course will be changing again when HTML5 is common, in a few years. To be honest, for backwards compatibility, we do give old IE browsers still an iframe. The current situation is simply such that object tags can be used to define frames. And in such frames offering a file download should work. |