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?

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.

<shaver> alecf's working on this stuff now, he says.

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..

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.

well then, dupe it is. *** This bug has been marked as a duplicate of 119923 ***