535 bytes, text/plain
927 bytes, application/octet-stream
1.49 KB, text/html
968 bytes, text/html
1.04 KB, text/html
Assignee: joe.chou → rogerl
Status: UNCONFIRMED → NEW
Component: OJI → Live Connect
Ever confirmed: true
QA Contact: pmac → pschwartau
Reassigning to OJI component; cc'ing Patrick.
Assignee: rogerl → joe.chou
Component: Live Connect → OJI
QA Contact: pschwartau → pmac
nominating for mozilla1.0 because <object><embed></embed><object> is used fairly often
Component: OJI → Live Connect
This is unlikely to be an OJI problem, more likely an object frame problem. Reassigning to peterl.
Assignee: joe.chou → peterl
Component: Live Connect → Plug-ins
I think there are two things to make the <embed> tag work in attachment #58997 [details]: 1. The patch in bug 108557. This will make us use the nested <embed> tag rather than the OBJECT. The patch needs super review. 2. The ID/NAME attributes of the OBJECT rand EMBED tags conflict. Using different names and applying the patch attchment #58294 makes the testcase work for me.
Status: NEW → ASSIGNED
marking nsbeta1-; bug 108557 has been plussed.
Keywords: nsbeta1 → nsbeta1-
Ok, I'm having some serious difficulty in fathoming the decision to ignore the <object> tag and use the <embed> tag????? The <embed> tag was a Netscape 4 proprietary thing. It isn't even mentioned in the html 4.0.1 spec, for god's sake! Seriously, what the hell? IE seems to have a dandy time with the <object> tag. I haven't tried Opera, but I'll bet they aren't going to do anything with the <embed> tag. If this is a "parity with Netscape 4" thing, just forget that. Netscape 4 sucked from the beginning, so why would Mozilla want parity with something that sucks anyway? To be fair there might have been some things that people liked about Netscape 4, but the proprietary <embed> tag most certainly was not one of them! The whole <object><comment><embed><noembed></noembed></embed><comment></object> is a kludge so that the Sun Java Plugin can be used with multiple browsers including Netscape 4. If we got rid of the Netscape 4 crap (can you say "dwindling market share" 5 times fast?), then we'd just use <object></object>. Now you are saying "let's continue with the Netscape 4 kludge in Mozilla/Netscape6"? Where is the logic there? Man, maybe I am just way late in the game and I missed all the important discussions about why we need to do this, but now I can't write a page that validates as html401 if I want to run an applet in Mozilla...but in IE, I can be standards compliant. Have I just stepped into Bizarro World???????? Am I way off base here? I think a *very* good explanation is in order before we commit to this because this crap is going to stick with us for a long time if Mozilla 1.0 doesn't support the <object> tag and continues to support the <embed> tag. Jake
Based on my comment #10 that bug 108557 is fixed, marking this WFM. btw, this bug is not about making the OBJECT tag work because it already does, but rather making the nested EMBED tag work.
Status: ASSIGNED → RESOLVED
Last Resolved: 16 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.