383831 - Gecko fails to display content that is attached to a web page with a simple object tag.

Status: RESOLVED DUPLICATE of bug 1156

(Core :: General, defect)

Description

[Toni Ruottu]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.4) Gecko/20061201 Firefox/2.0.0.4 (Ubuntu-feisty)
Build Identifier: 

This is a meta bug for tracking bugs related to object tag rendering failures, where some content, which is displayed correctly when typed to the browser address bar, fails to display when it is attached to a web page with an object-tag.

Reproducible: Sometimes

Steps to Reproduce:
1. Load a file directly into the browser
2. Attach the file to a web page with syntax <object data="file" />
3. Load the web page into browser
Actual Results:  
Displaying content directly succeeds.
Attached content does not get displayed.

Expected Results:  
Displaying content directly succeeds.
Displaying attached content succeeds.

Comment 1

[Christian :Biesinger (don't email me, ping me on IRC)]

as written, this sounds like a duplicate of bug 1156

Object loading has changed a lot for Firefox 3 and many bugs have been fixed, can you try Gran Paradiso?
http://developer.mozilla.org/devnews/index.php/2007/06/06/firefox-30-alpha-5-available-for-download/

Comment 2

[Toni Ruottu]

This is more general. So this is not a duplicate for 1156. 1156 is just a similar problem. I did for example declare mime-type for an atom feed, but Firefox 2 did not render the feed when it was included with object-tag on a web page. I have not tried this specific case with Firefox 3 yet, but this still works as an example how the bugs are different. This bug also considers cases where the mime-type is declared explicitly. Guessing mime-types for arbitrary data is a distinct issue.

Note: Firefox 2 was able to render a presentation for the feed when pointed directly at it.

Comment 3

[Christian :Biesinger (don't email me, ping me on IRC)]

Well, you'll have to give more concrete examples then. However, those kinds of bugs won't be fixed for Firefox 2, so you should probably test in FF3 instead.