Brummelchen wrote:i would cut the usage of userchrome.js at first. too intrusive for too much "beginners". the rest should start compiling its own firefox not to bother wiser people.
i also use a userchrome with few changes - safe modifications from Aris his collection.
(I'm sure there's a language issue in the way I'm reading it, & I'm not knocking you, but...)
There is nothing "beginner" with userChrome.js (IMO).
If a user is using userChrome.js, they are beyond, beginner.
And if userChrome.js is "too instrusive" for this "beginner", we're (FF is) now expecting these beginners to start compiling their own FF
.
Oh, & sorry, once FF removes userchrome, well..., your "safe modifications" are gone too.
But you can always compile your own
.
(Actually, userchrome is absolutely the wrong way to go about things. Only problem is, there is no other way, any longer.)
Fire 750, bring back 250.
Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 Pinball CopyURL+ FetchTextURL FlashGot NoScript