Closed Bug 82552 Opened 24 years ago Closed 20 years ago

nsCSSFrameConstructor doesn't support adding nested <object>s dynamically

Categories

(Core Graveyard :: Plug-ins, defect, P2)

x86
Windows 2000
defect

Tracking

(Not tracked)

RESOLVED WORKSFORME
Future

People

(Reporter: karnaze, Assigned: peterl-bugs)

References

Details

(Keywords: html4, regression, Whiteboard: [PL2:NA][HTML4-13.3])

Attachments

(2 files)

There are 2 cases in nsCSSFrameConstructor where a nested <object> could get appened or inserted but it would not process its children. Unfortunately, the following test case causes javascript code to assert, because the outer <object> can't instantiate a plugin (which it shouldn't). I'll file another bug on that. <HEAD> <SCRIPT> function doIt() { var object1 = document.getElementsByTagName("OBJECT")[0]; var object2 = document.createElement("OBJECT", null); object2.name = "video"; object2.Type = "audio/x-pn-realaudio-plugin" object2.src = "http://video.cnet.com/cnet/template/blank.rpm" object2.controls = "controlpanel"; object2.console = "ClipNN"; object2.width = "320"; object2.height = "36"; object1.appendChild(object2); } </SCRIPT> </HEAD> <BODY onload="doIt()"> <OBJECT id="videoieplay" classid="clsid:CFCDAA03-8BE4-11cf-B84B-0020AFBBCCFA" width="320" height="36" align="top"> </OBJECT> </BODY></HTML>
Moving to m0.9.2 because the risk is low, and I'm afraid that a long page with a plugin at the end might tickle it. This is a regression from the patch in bug 66645.
Status: NEW → ASSIGNED
Keywords: patch, regression
Priority: -- → P2
Target Milestone: --- → mozilla0.9.2
http://www.pravda.com.ua in bug 80683 appears to hit the javascript assertion, so I don't need to file a bug on that after all.
r=peterl
Kewl! sr=attinasi
This bug belongs with bug 64645, which will be reopened.
Blocks: 64645
Target Milestone: mozilla0.9.2 → mozilla0.9.3
Target Milestone: mozilla0.9.3 → mozilla0.9.4
Target Milestone: mozilla0.9.4 → mozilla0.9.5
Reassigning to av.
Assignee: karnaze → av
Status: ASSIGNED → NEW
Target Milestone: mozilla0.9.5 → mozilla0.9.6
Chris, I applied your patch but don't see any difference with the test case. What should be the effect? Is the patch out of date?
Maybe the patch in bug 64645 needs to be applied as well. I'm not sure if all of that patch got backed out or not, so check that.
more word needed --> 0.9.7
Target Milestone: mozilla0.9.6 → mozilla0.9.7
'work' that is...
Other things take my time for 0.9.7 -- pushing...
Target Milestone: mozilla0.9.7 → mozilla0.9.8
-> 0.9.9
Target Milestone: mozilla0.9.8 → mozilla0.9.9
moving to 1.0
Target Milestone: mozilla0.9.9 → mozilla1.0
Moving Netscape owned 0.9.9 and 1.0 bugs that don't have an nsbeta1, nsbeta1+, topembed, topembed+, Mozilla0.9.9+ or Mozilla1.0+ keyword. Please send any questions or feedback about this to adt@netscape.com. You can search for "Moving bugs not scheduled for a project" to quickly delete this bugmail.
Target Milestone: mozilla1.0 → mozilla1.2
confirmed the problem is still present, setting to PL2:NA
Assignee: av → peterl
Whiteboard: [PL2:NA]
Target Milestone: mozilla1.2alpha → mozilla1.0.2
Target Milestone: mozilla1.0.2 → Future
Keywords: html4
Whiteboard: [PL2:NA] → [PL2:NA][HTML4-13.3]
Attached file Testcase
Fixes some bugs in the original testcase here....
The image loads fine in a current trunk build. Marking worksforme.
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: