This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

This thread was archived. Please ask a new question if you need help.

With the latest update 52.5.2, the userChrome.css mod appears to now only work for FF, not TB.

  • 2 replies
  • 1 has this problem
  • 1 view
  • Last reply by Zenos

artisticdigital
artisticdigital
more options

on MacbookPro, osX 10.13.2, 15.5" retina monitor

The contents of my userChrome.css (it's in the right spot) file are:

@namespace url("http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul");

  • { 
  font-size:14pt!important;
  font-family:"Trebuchet MS";

}

This was working before latest update and is still effective in FF.

As a result, on my retina, the font being used for the message list is really, really small (see attached).

on MacbookPro, osX 10.13.2, 15.5" retina monitor The contents of my userChrome.css (it's in the right spot) file are: @namespace url("http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul"); * { font-size:14pt!important; font-family:"Trebuchet MS"; } This was working before latest update and is still effective in FF. As a result, on my retina, the font being used for the message list is really, really small (see attached).

All Replies (2)

artisticdigital
artisticdigital Question owner
more options

the screen cap of TB

Zenos
Zenos
more options

The screen capture really needs to show some "normal" sized text as well, so we can compare.

userChrome.css is still working here in Linux, and yes, I'm using TB 52.5.2 as well. I am puzzled because those reporting this don't consistently mention upgrading. The failure appears to have manifested suddenly and without apparent cause.

Has your OS undergone any updates recently?

Modified by Zenos