Closed Bug 42860 Opened 25 years ago Closed 25 years ago

nsIScriptNameSpaceManager::RegisterGlobalName should accept IIDs for xpidl objects

Categories

(Core :: DOM: Core & HTML, defect, P3)

x86
Windows NT
defect

Tracking

()

VERIFIED FIXED

People

(Reporter: vidur, Assigned: vidur)

Details

(Whiteboard: [nsbeta2+] [6/22])

Currently, objects can be added to the global namespace of DOM JavaScript contexts (i.e. as window properties) using the nsIScriptNameSetRegistry and nsIScriptNameSpaceManager interfaces. Since these interfaces were originally created before xpidl and XPConnect, the only types of objects that could be added via this mechanism were ones whose interfaces were specified in idlc. Currently, the RegisterGlobalName method only takes a name and a CID, precluding us from adding xpidl-specified objects to the global namespace. This will be a big problem for future extensibility of the product. In other words, we will be able to create new xpidl components, but won't be able to make them script visible. This is one of the bugs that I mentioned to Phil and Clayton as critical for being able to add in script visible features as modules after we ship.
Nominating for nsbeta2
Keywords: nsbeta2
nsbeta2+ until 6/22
Whiteboard: [nsbeta2+] [6/22]
Fix checked in on 6/20/2000. I guess I'm the one who's going to have to verify it, since it's purely a code change.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Verified on 6/21/2000.
Status: RESOLVED → VERIFIED
Component: DOM Level 2 → DOM Other
Component: DOM Other → DOM Level 1
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.