Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Avatar for Username

Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Weitere Informationen

Dieses Thema wurde archiviert. Bitte stellen Sie eine neue Frage, wenn Sie Hilfe benötigen.

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

  • 2 Antworten
  • 1 hat dieses Problem
  • 17 Aufrufe
  • Letzte Antwort von 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).

Alle Antworten (2)

artisticdigital
artisticdigital Fragesteller
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?

Geändert am von Zenos