Re: Installing xmlextras on Thunderbird [static build stuff?]

Axel Hecht wrote:
> Paul Sinnett wrote:

>> Does this mean I'm missing the bit that maps nsIDOMSerializer to the 
>> name XMLSerializer? If so, how do I go about installing that? All I 
>> have done so far is to copy the files run regxpcom...

> I have no clue, but this may really be more of an xpcom question.
> Maybe something tricky with static builds?

Okay, after a little more investigation. It appears that the file that
connects the name XMLSerializer to nsIDOMSerializer is called
compreg.dat. I have 4 versions of this file on my machine:

#locate compreg.dat
/usr/lib/MozillaThunderbird/components/compreg.dat
/usr/lib/MozillaFirefox/components/compreg.dat
/home/paul/.mozilla/firefox/default.2hb/compreg.dat
/home/paul/.thunderbird/default/0gxxmpcw.slt/compreg.dat

All of these, except the last one, contain the line:
JavaScript DOM class,[email protected]/xmlextras-domci-extender;1

So my analysis is that my user profile's compreg.dat doesn't know how to
map XMLSerializer and so scripts that use it return "XMLSerializer not
defined."

I've tried deleting the files and getting thunderbird to rebuild them,
but it always rebuilds them in the same way - ie. without xmlextras. If
I copy compreg.dat from the MozillaThunderbird/components directory then
I get a different error: "Factory not registered." But if I ignore that
and try to install an extension that uses XMLSerializer the compreg.dat
file is rewritten anyway and so I still get "XMLSerializer not defined."

Something inside thunderbird but outside of xpcom knows that I didn't
have xmlextras installed with thunderbird and removes it from
compreg.dat. Where is thunderbird getting its information from? It's
not from xpti.dat (I have 4 versions of this as well but they all
contain the xmlextras stuff.)