Re: userChrome.css and userContent.css disabled by default in Fx 69+
- Date: Fri, 24 May 2019 17:39:10 -0700
- From: The Real Bev <bashley101+moz@xxxxxxxxx>
- Subject: Re: userChrome.css and userContent.css disabled by default in Fx 69+
On 05/24/2019 05:26 PM, WaltS48 wrote:
On 5/24/19 5:42 PM, The Real Bev wrote:
On 05/24/2019 06:31 AM, »Q« wrote:
tl;dr: In Fx 69+, using userChrome.css and userContent.css will be
controlled by a pref which will be off in new profiles. Fx 68 will
toggle it on in profiles currently using either of those files.
BUT "Firefox users who use the files already will have the feature
enabled for them automatically to avoid disruptions to their workflows
This must be an error; I'm sure someone will put it right soon :-(
Did you read the "Timeline for the change(proposed, subject to change):
section of the blog post?
Sorry, I should have added a <sarcasm> tag.
I don't remember ever having to tell FF to use these files, they just
got sucked in automatically.
Right now users don't have to tell Firefox, SeaMonkey or Thunderbird to
use those files.
Users with new installs of version 69.0 will have to set the preference
Current and future new users still have to create those files and the
chrome directory in the profile.
An organizer for the "Million Agoraphobics March" expressed
disappointment in the turnout for last weekend's event.
general mailing list