Philip Chee wrote:

In GreaseMonkey 0.5 (when it still claimed Mozilla Suite compatibility) the 
install.js would install the extension part into the profile but register 
(DELAYED_CHROME) the extension in the app/global chrome.rdf. Now, that's, well, 
strange. I wonder why they did it that way?
They probably couldn't figure out why they couldn't load a profile chrome script into a global component, so they simply registered the chrome globally too; of course they should have installed the chrome globally too.
_______________________________________________
Project_owners mailing list
[email protected]
http://mozdev.org/mailman/listinfo/project_owners

Reply via email to