Web lists-archives.com

Re: userChrome.css will not be supported indefinitely

My bloviated meandering follows what WaltS48 graced us with on 1/30/2018 11:30 AM:
On 1/30/18 2:22 PM, Ed Mullen wrote:
On 1/30/2018 at 2:17 PM, WaltS48 created this epitome of digital genius:
On 1/30/18 2:01 PM, Wolf K wrote:
On 2018-01-30 13:06, Ed Mullen wrote:
On 1/30/2018 at 1:01 PM, Caver1 created this epitome of digital genius:
"The functionality of userChrome.css will not be supported, for the same reasons that we removed support for legacy themes."

I just uttered language I cannot post here.

I bet I had the same thoughts.

So, you all want somebody to hack into your userContent.css, or userChrome.ccs files and hijack your Firefox.


Oh, c'mon!  Just how are they going to do that?

The same way they could with Complete Themes I guess.

Hack into your computer, edit the files and save them. Or maybe completely replace them.

The next time you open Firefox, it doesn't look like you last used it.

That seems a bit specious. Mozilla allows anyone to hack the or hijack their own Firefox if the wanted to build their own version. Userchrome.css only allows style changes and NOT executable code like javascript. Sure, I could, with a little effort switch a "Yes" and "Cancel" button images but that's self-inflicted and not something anyone would want to do on their on browser, no?

Rare Mozilla Stuff: http://tinyurl.com/z86x3sg
general mailing list