Closed Bug 68832 Opened 24 years ago Closed 22 years ago

Chrome Registry should have "simple" mode that doesn't load RDF

Categories

(Core :: XUL, defect)

PowerPC
Mac System 8.5
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 119923
mozilla1.1beta

People

(Reporter: hyatt, Assigned: alecf)

References

Details

The chrome registry should have a pref that enables you to just hardcode to
certain JARs, without having to depend on RDF.  Useful for those who are cutting
out XUL completely.
For saving footprint in embedding, this would be good. Although to have chrome
not load RDF, only to have some other component load it anyway would not be
good. What are some other users of RDF that we would have to avoid/alter in
order to do this?
Blocks: 69995
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla0.9
I think the right way to patch this is to just find everybody who tries to
instantiate the chrome registry and have them do something else if the chrome
registry load fails.
I meant the getservice.
Target Milestone: mozilla0.9 → mozilla0.9.1
Target Milestone: mozilla0.9.1 → mozilla1.0.1
<shaver> alecf's working on this stuff now, he says.
Assignee: hyatt → alecf
Status: ASSIGNED → NEW
Keep me in the loop on this, and ignore my last comment.  I think you 
should just hack the chrome registry itself and not try to patch all the 
callers.
I really really want to mark this a dupe of bug 119923
Should I? I'm leaning towards a new, super-lightweight implementation..
Status: NEW → ASSIGNED
I think it would be better as a dup of bug 119923. I don't think the chrome reg
should be hacked for this, but a lightweight component with the same contract id
as the heavyweight chrome reg should be made. If the simple impl suffices for an
embedding app, just use that one instead.
Keywords: mozilla1.0+
Target Milestone: mozilla1.0.1 → mozilla1.1beta
well then, dupe it is.

*** This bug has been marked as a duplicate of 119923 ***
Status: ASSIGNED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.