Pretraži podršku

Izbjegni prevare podrške. Nikad te nećemo tražiti da nas nazoveš, da nam pošalješ telefonski broj ili da podijeliš osobne podatke. Prijavi sumnjive radnje pomoću opcije „Prijavi zlouporabu”.

Saznaj više

Thunderbird 78.7.1 Folder Pane line spacing

  • 1 odgovor
  • 1 ima ovaj problem
  • 1 prikaz
  • Posljednji odgovor od dlpoole

more options

The Mint20 software updater just pushed a TB update from 68.1.0 to 78.7.1 and now, I too have a folder pane full of useless whitespace between folders.

I've read what I believe to be every one of the threads on this problem in 78.3.x, but even after setting toolkit.legacyUserProfileCustomizations.stylesheets true, locating the current profile folder, and creating the /Chrome/userChrome.css file, *none* of the various .css hacks suggested for reversing this change or regression work in 78.7.1. All such changes are ignored.

If anyone has a way of reversing this bug or regression in 78.7.1, I'd surely appreciate it.

The Mint20 software updater just pushed a TB update from 68.1.0 to 78.7.1 and now, I too have a folder pane full of useless whitespace between folders. I've read what I believe to be every one of the threads on this problem in 78.3.x, but even after setting toolkit.legacyUserProfileCustomizations.stylesheets true, locating the current profile folder, and creating the /Chrome/userChrome.css file, ''*none*'' of the various .css hacks suggested for reversing this change or regression work in 78.7.1. All such changes are ignored. If anyone has a way of reversing this bug or regression in 78.7.1, I'd surely appreciate it.

Izabrano rješenje

Guess I can't edit and must reply to my own thread. I corrected the spelling of the path to /chrome/userChrome.css and now one of the .css changes is working. Never mind, though for the record, I hate gratuitous changes and regressions to user interfaces.

Pročitaj ovaj odgovor u kontekstu 👍 0

Svi odgovori (1)

more options

Odabrano rješenje

Guess I can't edit and must reply to my own thread. I corrected the spelling of the path to /chrome/userChrome.css and now one of the .css changes is working. Never mind, though for the record, I hate gratuitous changes and regressions to user interfaces.