Mozilla VPN is currently experiencing an outage. Our team is actively working to resolve the issue. Please check the status page for real-time updates. Thank you for your patience.

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.

Why has Firefox 3.6.28 for PPC suddenly stopped reading stylesheets?

  • 2 replies
  • 3 have this problem
  • 4 views
  • Last reply by rocjet

rocjet
rocjet
more options

Yesterday, Firefox 3.6.28 running on a PPC Mac OSX 10.5.8 stopped reading stylesheets. Displays pages without style attributes.

Yesterday, Firefox 3.6.28 running on a PPC Mac OSX 10.5.8 stopped reading stylesheets. Displays pages without style attributes.

Chosen solution

Make sure that you haven't enabled a High Contrast theme in the Windows/Mac Accessibility settings and that you allow pages to choose their colors in Firefox.

  • Firefox > Preferences > Content : Fonts & Colors > Colors : [X] "Allow pages to choose their own colors, instead of my selections above"
Read this answer in context 👍 1

All Replies (2)

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

Chosen Solution

Make sure that you haven't enabled a High Contrast theme in the Windows/Mac Accessibility settings and that you allow pages to choose their colors in Firefox.

  • Firefox > Preferences > Content : Fonts & Colors > Colors : [X] "Allow pages to choose their own colors, instead of my selections above"
rocjet
rocjet Question owner
more options

Brilliant thanks! I have never visited that pane in preferences before, but checking the option fixed the problem. None the wiser if it was checked previously or if something else has occurred that makes checking now necessary...