Closed Bug 93082 Opened 24 years ago Closed 24 years ago

FIX xpccomponets.cpp use of scriptable to deal better with prototype use

Categories

(Core :: XPConnect, defect, P3)

defect

Tracking

()

VERIFIED WORKSFORME
mozilla0.9.7

People

(Reporter: dbradley, Assigned: dbradley)

Details

Attachments

(1 file)

The issue here is that the scriptable handlers in the classes in xpccomponents.cpp may not really do the right thing when the JSObjects are used as protos of other JSObjects. I *think* these methods assume that the target object of a call is the same object that is the JSObject of the wrapper rather than checking the object that was passed in.
Status: NEW → ASSIGNED
Priority: -- → P3
Target Milestone: --- → mozilla1.0
Target Milestone: mozilla1.0 → mozilla0.9.6
Target Milestone: mozilla0.9.6 → mozilla0.9.7
I created the attached JS code to try and demonstrate the problem. My assumption is that if it had the wrong object the property would get defined on the object instead of the prototype and thus stick around after the prototype was reset. I've learned not to trust my assumptions, though ;-) The test doesn't show any problems.
Marking this WORKSFORME for previos comments reasons.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
Yeah, I'm not seeing any places in the code that look wrong either.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: