Closed
Bug 73747
Opened 24 years ago
Closed 24 years ago
JS components global should use lazy JS_ResolveStandardClass
Categories
(Core :: XPConnect, defect)
Tracking
()
VERIFIED
FIXED
mozilla0.9.1
People
(Reporter: brendan, Assigned: jband_mozilla)
References
()
Details
Same for XPConnect's safe context, if it controls the global class. Nuff said.
/be
Assignee | ||
Comment 1•24 years ago
|
||
This is mine. I'm fixing this on my flattening branch. The scheme for
nsIXPConnnect::InitClassesWithNewWrappedGlobal used in the loader has changed
some and any change to the trunk loader would just conflict.
Assignee: shaver → jband
Assignee | ||
Comment 2•24 years ago
|
||
I just checked in a fix for this to jband_xpconnect_flattening_BRANCH.
Status: NEW → ASSIGNED
Assignee | ||
Updated•24 years ago
|
Target Milestone: --- → mozilla0.9.1
Assignee | ||
Updated•24 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 3•24 years ago
|
||
fixed by XPCDOM_20010329_BRANCH landing
You need to log in
before you can comment on or make changes to this bug.
Description
•