Re: userChrome.css will not be supported indefinitely
- Date: Wed, 31 Jan 2018 09:34:41 -0500
- From: Tanstaafl <tanstaafl@xxxxxxxxxxxxxxx>
- Subject: Re: userChrome.css will not be supported indefinitely
On 1/30/2018, 2:17:13 PM, WaltS48 <WaltS48@xxxxxxxxxxxxxxxxx> 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.
Oh, god, that is the same ridiculous fear mongering used to justify the
ridiculous requirement for Signed Addons, that was shown to be easily
The bottom line is, there is a huge difference between an active
exploit, and a THEORETICAL one.
All of this is purely theoretical.
Please provide one - JUST ONE - instance where this has happened, in the
millions of man years that Thunderbird has been used with this capability.
general mailing list