Avatar for Username

Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Learn More

Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.

New update not compatible with full themes... Unacceptable!!!

  • 2 antwurd
  • 1 hat dit probleem
  • 1 werjefte
  • Lêste antwurd fan Allanlaigh

Allanlaigh
Allanlaigh
more options

Since the update to 57.0 (64 bit), I cannot use a full theme (everything available is not compatible any more), hence I am facing blindingly white pages in many occasions, which is very tiring... so tiring, I am thinking of switching again to Chrome! Anyone any ideas? Please, my eyes cannot stand much more of this! (I am using a TV connected to the PC, you can imagine the whiteness!)...

Since the update to 57.0 (64 bit), I cannot use a full theme (everything available is not compatible any more), hence I am facing blindingly white pages in many occasions, which is very tiring... so tiring, I am thinking of switching again to Chrome! Anyone any ideas? Please, my eyes cannot stand much more of this! (I am using a TV connected to the PC, you can imagine the whiteness!)...

Alle antwurden (2)

Mkll
Mkll
more options

Hello, Complete Theme support was axed back in Firefox 48. If you wish for something similar, you can create a userChrome.css file and make all the customizations you want! To do so, follow the documentation here: https://www.userchrome.org/how-create-userchrome-css.html

Some cool things you can do with it see here: https://reddit.com/r/FirefoxCSS

Allanlaigh
Allanlaigh Fraacheigener
more options

Thank you for trying to help, but I have no intention of getting into page programming, not even a little... I was very satisfied with my full theme and would like to have that capability back... I don't know what the big deal is to allow for this kind of customization, or why the capability was knocked out with the update. It should be fixed. But, again, thank you for trying to help! :)