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!

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

Hierdie gesprek is in die argief. Vra asseblief 'n nuwe vraag as jy hulp nodig het.

Constant errors, hang, all sites, including this

tommymiles
tommymiles
more options

Windows &, new install (work), new Dell Optiplex 390, new install of FF 20.0.1

Pretty much constant hangs. FF unresponsive for over a minute on most pageloads (news.google.com, Washington post, Yahoo, ABC news, etc) Error console fills up after hang ends with errors and warning on css properties, js errors, etc. Seems especially prevelent (but not limited to) new tabs.

Looking at about 3 dozen errors for this site. Examples include

Timestamp: 4/17/2013 1:59:41 PM

Warning: Expected declaration but found '*'. Skipped to next declaration. Source File: http://support.cdn.mozilla.net/media/css/common-min.css?build=0021b54 Line: 1


Google news in another tab (sitting, while working on this tab) just produced another "stopped script" warning.

A few dozen more error log entries, examples include

Timestamp: 4/17/2013 2:11:05 PM Warning: Unknown property '-moz-border-radius'. Declaration dropped. Source File: http://s.ytimg.com/yts/cssbin/www-embed-vfl0pSeeF.css Line: 1

Timestamp: 4/17/2013 2:15:34 PM Warning: Expected media feature name but found 'modernizr'. Source File: http://support.mozilla.org/en-US/questions/933149 Line: 1

Timestamp: 4/17/2013 2:15:34 PM Warning: Expected color but found 'top'. Error in parsing value for 'background-image'. Declaration dropped. Source File: http://support.cdn.mozilla.net/media/css/common-min.css?build=0021b54 Line: 1


Timestamp: 4/17/2013 2:11:05 PM Warning: Error in parsing value for 'background-image'. Declaration dropped. Source File: http://s.ytimg.com/yts/cssbin/www-embed-vfl0pSeeF.css Line: 1

Windows &, new install (work), new Dell Optiplex 390, new install of FF 20.0.1 Pretty much constant hangs. FF unresponsive for over a minute on most pageloads (news.google.com, Washington post, Yahoo, ABC news, etc) Error console fills up after hang ends with errors and warning on css properties, js errors, etc. Seems especially prevelent (but not limited to) new tabs. Looking at about 3 dozen errors for this site. Examples include Timestamp: 4/17/2013 1:59:41 PM Warning: Expected declaration but found '*'. Skipped to next declaration. Source File: http://support.cdn.mozilla.net/media/css/common-min.css?build=0021b54 Line: 1 Google news in another tab (sitting, while working on this tab) just produced another "stopped script" warning. A few dozen more error log entries, examples include Timestamp: 4/17/2013 2:11:05 PM Warning: Unknown property '-moz-border-radius'. Declaration dropped. Source File: http://s.ytimg.com/yts/cssbin/www-embed-vfl0pSeeF.css Line: 1 Timestamp: 4/17/2013 2:15:34 PM Warning: Expected media feature name but found 'modernizr'. Source File: http://support.mozilla.org/en-US/questions/933149 Line: 1 Timestamp: 4/17/2013 2:15:34 PM Warning: Expected color but found 'top'. Error in parsing value for 'background-image'. Declaration dropped. Source File: http://support.cdn.mozilla.net/media/css/common-min.css?build=0021b54 Line: 1 Timestamp: 4/17/2013 2:11:05 PM Warning: Error in parsing value for 'background-image'. Declaration dropped. Source File: http://s.ytimg.com/yts/cssbin/www-embed-vfl0pSeeF.css Line: 1

All Replies (1)

jscher2000 - Support Volunteer
jscher2000 - Support Volunteer
  • Top 25 Contributor
more options

Hi tommymiles, don't worry about style warnings; in order to cater to older browsers and special browser-specific features, websites commonly use many rules that Firefox considers invalid.

Most major websites are pulling in resources from numerous servers, potentially a dozen or more, and Firefox often seems to wait on the slowest one. Still, Google News should work fine, so there's something else going on here.

If you decide to do further troubleshooting, check out this article and see whether any of the issues are relevant to you: Firefox hangs or is not responding - How to fix.