Nested <object> tags seem to break the IcedTea plugin




9 years ago
8 years ago


(Reporter: Steve Hill, Unassigned)


Firefox Tracking Flags

(Not tracked)


(Whiteboard: [CLOSEME 2010-11-01], URL)



9 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv: Gecko/2008102718 Fedora/3.0.2-1.fc10 Firefox/3.0.2
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv: Gecko/2008102718 Fedora/3.0.2-1.fc10 Firefox/3.0.2

I'm not entirely sure if this is a FireFox bug or an IcedTea bug.  However, I don't see why IcedTea should ever get to see the actual DOM tree, so I'm going to assume it is a FireFox bug for now:

If a web page has a Java applet which has been embedded with the <object> tag, nesting another <object> tag within it seems to prevent the IcedTea plugin from running the applet.  The following is reported on stderr:

Initializing JVM...
NOT IMPLEMENTED: virtual nsresult IcedTeaPluginInstance::Start()
Warning: <object> tag requires code attribute.

(Note: The W3C do not specify the existence of a "code" attribute for the <object> tag).

Reproducible: Always

Steps to Reproduce:
1. Visit with the IcedTea plugin installed

Actual Results:  
Java applet remains a grey box and stderr reports "Warning: <object> tag requires code attribute."

Expected Results:  
Java applet should run.

The following URI is an identical page, but with the nested <object> tag replaced with an <img> tag - this page works correctly and does not produce the "Warning: <object> tag requires code attribute." message:
This is a mass search for bugs which are in the Firefox General component, are
UNCO, have not been changed for 500 days and have an unspecified version. 

Reporter, can you please update to Firefox 3.6.10 or later, create a fresh profile,, and test again. If you still see the issue, please update this bug. If the issue is gone, please set the status to RESOLVED > WORKSFORME.
Whiteboard: [CLOSEME 2010-11-01]
No reply from reporter, INCOMPLETE. Please retest with Firefox 3.6.12 or later and a new profile ( If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Last Resolved: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.