Closed
Bug 341834
Opened 18 years ago
Closed 6 years ago
Find a better way for XPConnect global objects to be JS global objects
Categories
(Core :: XPConnect, defect)
Tracking
()
RESOLVED
INACTIVE
People
(Reporter: mrbkap, Unassigned)
Details
The patch for bug 339041 allowed XPConnect global objects to have JSCLASS_GLOBAL_FLAGS. I'm extremely unhappy with that patch, however. There are cases that it doesn't cover (where it's possible for us to create a class which has the wrong flags) and it's extremely invasive.
I still think that we should add an nsIXPCScriptable flag for this purpose, since that's the only information available to XPCNativeScriptableShared::PopulateClass, which is really where we need the info to be.
Updated•18 years ago
|
Assignee: dbradley → nobody
Comment 1•6 years ago
|
||
Per policy at https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Inactive_Bugs. If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → INACTIVE
You need to log in
before you can comment on or make changes to this bug.
Description
•