Re: userChrome.css will not be supported indefinitely
- Date: Tue, 30 Jan 2018 13:24:40 -0800
- From: The Real Bev <bashley101+moz@xxxxxxxxx>
- Subject: Re: userChrome.css will not be supported indefinitely
On 01/30/2018 11:17 AM, WaltS48 wrote:
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.
I think I've mentioned before that the average burglar would take one
look and decide that we'd already been looted and trashed and go on to
the next house. Should he, however, decide to steal our computer(s)
he'd play hell finding and reaching the wires necessary to remove them,
much less being able to actually extricate them from the mass of junk
that surrounds them.
Having given up on trying to steal some old HEAVY computers, however,
and still wishing to violate our .css files, upon turning on the
computers he would be confronted with a simple prompt. He would then
have to find and choose which file(s) to violate. I have a lot of them.
Typing 'firefox' would just give him an error message.
At this point his only option would be to wake us up and demand that we
alter our .css files, call a friend who knows what to do, call some sort
of help line and listen to bad music for a few hours, or just give up
and walk away.
If I know that chaining yourself to a dead cow is stupid,
how come Carly makes so much more money than I do?
general mailing list