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

New Firefox Version does not CSS files

more options

So I bought a new router to configure via a website in Firefox. The computer I was using had Firefox 43.0 and the everything was fine. CSS loaded nicely, website response was great. Then I decided to look to see what version I had, Oh what a big mistake that was. After opening the About Firefox window to check what version I was on, all of a sudden The browser is asking me to restart the browser because it found an update. So I click the restart Firefox Button. Upon going back into the NEW firefox, I noticed a major problem right away. The page was missing, it's CSS file. Apparently the NEW Firefox does not want to load the CSS Page for some websites. So I had to change to a different browser just so I can finish programming my new Router.

Then this morning, I had a couple of my customers call me up because their Facebook page was blank. We verified that the problem was a Firefox bug only. So first, we lost pluggin support, now we loose CSS files. To me it looks like we are going backwards.

So I bought a new router to configure via a website in Firefox. The computer I was using had Firefox 43.0 and the everything was fine. CSS loaded nicely, website response was great. Then I decided to look to see what version I had, Oh what a big mistake that was. After opening the About Firefox window to check what version I was on, all of a sudden The browser is asking me to restart the browser because it found an update. So I click the restart Firefox Button. Upon going back into the NEW firefox, I noticed a major problem right away. The page was missing, it's CSS file. Apparently the NEW Firefox does not want to load the CSS Page for some websites. So I had to change to a different browser just so I can finish programming my new Router. Then this morning, I had a couple of my customers call me up because their Facebook page was blank. We verified that the problem was a Firefox bug only. So first, we lost pluggin support, now we loose CSS files. To me it looks like we are going backwards.

All Replies (2)

more options

Hi, Well as you would know bugs happen and should be reported here : If you have a bug, file a bug report. https://bugzilla.mozilla.org/ Bug Writing Guidelines : https://developer.mozilla.org/en-US/docs/Mozilla/QA/Bug_writing_guidelines

As you also must know Firefox works just fine with CSS when the CSS code is coded properly. That code can always be checked here : https://jigsaw.w3.org/css-validator/ and HTML checked here : https://validator.w3.org/ as W3C.org (World Wide Web Consortium) in charge of standards and practices and future development of web pages and web browsers make the rules on code. Mozilla Firefox follows these rules. This should help you with your customers : https://support.mozilla.org/en-US/kb/firefox-support-troubleshooting-guide

So if still having issue : uninstall Firefox. Then Delete the Mozilla Firefox Folders in C:\Program Files , C:\Program Files(x86) & C:\ProgramData Then restart system. Then run Windows Disk Cleanup. (Note: This should be Pinned and run Weekly, If never done below expect 10's of gig's) Then run it again and click the button that says Cleanup System Files. Note: your Firefox Profile is saved. But you should make a back up before you do :

Reinstall with Current Release Firefox 59.0.1 with a Full Version Installer

Please let us know if this solved your issue or if need further assistance.

more options

Hi ecornell, could you check with your router manufacturer on whether any updates are available? It's pure guesswork otherwise as to what might be going wrong with its page.

Then this morning, I had a couple of my customers call me up because their Facebook page was blank. We verified that the problem was a Firefox bug only. So first, we lost pluggin support, now we loose CSS files. To me it looks like we are going backwards.

Was it the issue affecting users who disabled ClearType font smoothing in their Windows settings? That is scheduled to be fixed in Firefox 59.0.2, with a temporary workaround of disabling hardware acceleration on the Options page.

Apparently the beta test population does not have enough users who disable ClearType, as the problem appears not to have been reported until after Firefox 59 was released. This kind of thing happens from time to time. We need more testers.