This thread was archived. Please ask a new question if you need help.
Firefox isn't accessing some CSS unless manually told to
Any website I visit, whether for the first time or the ten thousandth, has about a 50/50 chance of rendering without any CSS. Sometimes a site will load fine, but other times it loads as a white page with a long vertical list of links, images and text, all without formatting.
I have searched and searched for solutions to this problem. I disabled all add-ons, ran Firefox in safe mode, reset Firefox, cleared the cache, cleared cookies, made sure the settings allow websites to specify their own colors and fonts. Sometimes doing these things will buy me a little peace; usually not. It's hard to say because each website has such a random chance to mess up.
Normally, I can fix the problem by hitting refresh 1-5 times. Eventually, Firefox retrieves the CSS and everything works. I recently discovered Shift + Ctrl + R for an instant fix. However, I have no way of knowing if that fixed the problem for good for that website, since the next time I visit it, it could be fine or it could mess up again.
Amazingly, I don't think Facebook has ever had this problem for me. Netflix, Gmail, random internet forums, however, all have. There's really no pattern that I can see. The only reason I even know (suspect) it's a problem with the CSS is from all the research into people with similar problems.
Currently, I have NO add-ons running.
All Replies (20)
What security software do you have? It is possible that something is corrupting your cache.
Just Norton AntiVirus, which I've had all along; nothing about this or the way I use it has changed recently. How do I find out if that or something else is corrupting my cache?
Also important: how do I fix the corruption?
Update: Shift + Ctrl + R does not always work, apparently.
Have been to CNN.com before, but not since I cleared out the cache and cookies. Went to a new article, got the attached result (which took forever to load, too). When it finally finished, I hit Shift + Ctrl + R - it went through a reload motion, but the display didn't change. I tried that several times with no results, then just hit the normal refresh button and it fixed it.
You can try to open the Web Console (Web Developer > Web Console;Ctrl+Shift+K) and check the Network Log for errors if you do a hard reload (Ctrl+F5) or a normal reload (F5) to see if all files are retrieved without errors.
I have no idea what to do with any of this, but I opened the Web Console and copied the results after I encountered another error. This is after a hard reload:
[20:45:06.998] Error in parsing value for 'background-image'. Declaration dropped. @ http://movies.netflix.com/Queue?lnkctr=mhbqueInstant&qtype=ED [20:45:06.999] Expected ':' but found 'backgro'. Declaration dropped. @ http://movies.netflix.com/Queue?lnkctr=mhbqueInstant&qtype=ED -- [20:45:39.604] GET http://movies.netflix.com/Queue?lnkctr=mhbqueInstant&qtype=ED [HTTP/1.1 200 OK 2028ms] [20:45:41.364] GET http://cdn1.nflxext.com/FilePackageGetter/sharedSystem/pkg-nflxrsrc-0000000000048b1356a3e020018518180000102c8000-1344472542-1-5.css?v=1 [HTTP/1.1 200 OK 104ms]
[20:45:42.327] GET http://cdn1.nflxext.com/FilePackageGetter/sharedSystem/pkg-nflxrsrc-bfbfe0bea63c4000000000f2f0066444d8692404100103c3f9e12dd80004210-1344473468-1-5.js?v=1 [HTTP/1.1 200 OK 206ms] [20:45:42.365] GET http://cdn-0.nflximg.com/en_us/ffe/headers/header_icons_sprite.png [HTTP/1.1 200 OK 241ms] [20:45:42.368] GET http://cdn-0.nflximg.com/en_us/layout/page_titles/bgvignette/950w/blank_tan_vig.jpg [HTTP/1.1 200 OK 238ms] [20:45:42.370] GET http://cdn-0.nflximg.com/en_us/buttons/v7/bg.png [HTTP/1.1 200 OK 173ms] [20:45:42.372] GET http://cdn-0.nflximg.com/en_us/layout/ratings/starbar_unified.gif [HTTP/1.1 200 OK 231ms] [20:45:42.374] GET http://cdn-0.nflximg.com/en_us/pages/queue/q-sprites.gif [HTTP/1.1 200 OK 167ms] [20:45:42.377] GET http://cdn-0.nflximg.com/en_us/ffe/headers/miscellaneous_icons.png [HTTP/1.1 200 OK 218ms] [20:45:42.836] GET http://contactus.netflix.com/supportscript?_=1344559542660 [HTTP/1.1 302 Moved Temporarily 78ms] [20:45:42.889] GET https://contactus.netflix.com/supportscript?_=1344559542660 [HTTP/1.1 200 OK 93ms]
Modified by cor-el
All files that show in the log are retrieved without problems.
Can you post such a log when the page didn't load properly?
You can hide CSS errors by unchecking the items under the CSS button, so only the GET lines from the NET log remain.
Sure. This time, the website didn't work, I opened the console, did a normal refresh, and the formatting was still absent. This is what the console showed:
[22:08:09.729] GET http://movies.netflix.com/RateMovies [HTTP/1.1 200 OK 604ms] [22:08:10.229] GET http://cdn1.nflxext.com/FilePackageGetter/sharedSystem/pkg-nflxrsrc-000000000000831b56a3e028100508180000122e000-1344472542-1-5.css?v=1 [undefined 1ms] [22:08:10.277] GET http://cdn-7.nflximg.com/images/9380/529380.jpg [HTTP/1.1 200 OK 136ms] [22:08:10.280] GET http://cdn-0.nflximg.com/images/4501/514501.jpg [HTTP/1.1 200 OK 736ms] [22:08:10.282] GET http://cdn-6.nflximg.com/images/3990/533990.jpg [HTTP/1.1 200 OK 269ms] [22:08:10.304] GET http://cdn-8.nflximg.com/images/5816/495816.jpg [HTTP/1.1 200 OK 696ms] [22:08:10.306] GET http://cdn-7.nflximg.com/images/7131/597131.jpg [HTTP/1.1 200 OK 66ms] [22:08:10.309] GET http://cdn-6.nflximg.com/images/4799/1604799.jpg [HTTP/1.1 200 OK 86ms] [22:08:10.311] GET http://cdn-5.nflximg.com/images/9079/1299079.jpg [HTTP/1.1 200 OK 6785ms] [22:08:10.314] GET http://cdn-4.nflximg.com/images/1087/601087.jpg [HTTP/1.1 200 OK 204ms] [22:08:10.319] GET http://cdn-3.nflximg.com/images/6051/596051.jpg [HTTP/1.1 200 OK 223ms] [22:08:10.325] GET http://cdn-5.nflximg.com/images/9173/589173.jpg [HTTP/1.1 200 OK 6790ms] [22:08:10.335] GET http://cdn-3.nflximg.com/images/1097/591097.jpg [HTTP/1.1 200 OK 337ms] [22:08:10.339] GET http://cdn-7.nflximg.com/images/8780/588780.jpg [HTTP/1.1 200 OK 190ms] [22:08:10.342] GET http://cdn-7.nflximg.com/images/5849/595849.jpg [HTTP/1.1 200 OK 78ms] [22:08:10.345] GET http://cdn-0.nflximg.com/images/4591/534591.jpg [HTTP/1.1 200 OK 268ms] [22:08:10.348] GET http://cdn-9.nflximg.com/images/5438/495438.jpg [HTTP/1.1 200 OK 2730ms] [22:08:10.350] GET http://cdn-0.nflximg.com/images/4987/594987.jpg [HTTP/1.1 200 OK 299ms] [22:08:10.352] GET http://cdn-3.nflximg.com/images/4632/594632.jpg [HTTP/1.1 200 OK 618ms] [22:08:10.355] GET http://cdn-0.nflximg.com/images/6151/596151.jpg [HTTP/1.1 200 OK 286ms] [22:08:10.357] GET http://cdn-4.nflximg.com/images/8333/498333.jpg [HTTP/1.1 200 OK 324ms] [22:08:10.360] GET http://cdn-1.nflximg.com/images/5196/535196.jpg [HTTP/1.1 200 OK 73ms] [22:08:10.777] GET http://cdn1.nflxext.com/FilePackageGetter/sharedSystem/pkg-nflxrsrc-b9bfe0beae3c400000000002f0064444d849404100103c3f9e92dd003071310-1344473468-1-5.js?v=1 [undefined 1ms]
Modified by cor-el
The CSS file in the first GET shows an [undefined 1ms] response, so it looks that the file didn't get though to Firefox.
You can click such an entry to see the HTTP response headers for more information.
I clicked on the line with the undefined 1ms line and was only able to get Request Headers:
Accept:text/css,*/*;q=0.1 Accept-Encoding:gzip, deflate Accept-Language:en-us,en;q=0.5 Connection:keep-alive DNT:1 Host:cdn1.nflxext.com Referer:http://movies.netflix.com/RateMovies User-Agent:Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20100101 Firefox/14.0.1
This is what popped up for the very first GET (which displays [HTTP/1.1 200 OK 604ms] ); I've only included the response headers:
Cache-Control:private Connection:keep-alive Content-Encoding:gzip Content-Type:text/html;charset=UTF-8 Date:Fri, 10 Aug 2012 02:08:13 GMT Expires:Thu, 09 Aug 2012 02:08:13 GMT Pragma:no-cache Server:Apache-Coyote/1.1 Set-Cookie:tlr=US|1344564493339; Domain=.netflix.com; Expires=Mon, 05-Aug-2013 02:08:13 GMT JSESSIONID=E14BC4F010241FD3D40A822DB317ED20; Path=/ Transfer-Encoding:chunked Vary:Accept-Encoding Via:1.1 nflx X-Netflix.client.instance:i-1906b762 x-ua-compatible:IE=edge
Modified by cor-el
By the way, thanks a ton for your help on this. I've been pulling my hair out going at it alone and all of this is way above my head.
I tried to clean up the code I put in there, but it removed all my line breaks when it posted. Sorry for the jumble.
I've cleaned it up and formatted it.
Sorry, I meant the second request for the CSS file that has the [undefined 1ms] response.
Modified by cor-el
Like I said, I did click on the undefined line and it only displayed request headers - no response headers. The problem has magically become much rarer in the past few days, though it's still happening. The next time it does, I'll try to check again and see if I can get response headers for an [undefined 1ms] line - unless the fact that there were no response headers tells you anything?
Yeah, it just happened again - any time I get an 'undefined' and I click on that line, Firefox only shows me request headers - no response headers.
If there aren't any response headers then it looks that the request wasn't received by the server or the response headers were blocked and didn't arrive in Firefox (less likely because then there would be data send as well).
Such blocking is likely to be caused by security software (firewall) that doesn't give Firefox full access or takes too much time to process the send and received data.
I moved to a new home recently and I'm using the wireless network that was already here. I haven't changed any of my Norton settings. The other people in the house haven't reported similar experiences while browsing, but I'm not sure if they use Firefox.
Are there some steps I can take to troubleshoot the wireless network? I'm wondering if its settings might be causing the lag time you mentioned.
Bumping for help; this is still an ongoing problem for me and I really don't want to give up Firefox to solve it. I'd really appreciate if anyone could provide more advice from this point, even if it's to point me to another forum.
You could try the new Reset feature. This duplicates certain key data from your active settings folder into a new one, bypassing some add-ons and custom settings. Your plugins will still be active, but you should have a sparkly clean cache folder.
More information in this article: Refresh Firefox - reset add-ons and settings.
If the new settings folder (AKA Firefox profile) has the same problem, you can switch back using Firefox's Profile Manager. (This article describes how to start Firefox in the profile manager. I do not recommend removing anything until you are 110% certain that you will never need any of that profile's data in the future. Profile Manager - Create, remove or switch Firefox profiles)
Does it make any difference?
Resetting it was one of the first things I tried, once I started looking through forum posts from users with similar-sounding problems. It doesn't seem to have helped. :(
Sorry, I missed that in your description. Didn't read far enough up.
Does your Norton software have a reputation feature where it checks URLs against a database in the cloud before they are loaded? If so, could you try disabling that feature temporarily in case it is having problems.
For a request that doesn't return a result, is there a cookie section in that pop-up from the console? It usually would appear below the Request headers. If you can compare the cookie section from a successful request and an unsuccessful request to the same host, or after a refresh, for the same file, do you notice any difference?
I honestly don't know the answer to your question about Norton. I THINK the answer is no, it's not checking websites before giving me access to them, but I don't know enough about the software to be 100% sure. I can tell that there's a feature on it that performs a reputation check for applications, but I don't see anything about a similar protocol for websites.
I haven't been able to get a website to mess up when I have the console open lately (and once I open it and hit refresh, the page has been working more regularly). However, I remember that when I was looking at that pop-up window on an unsuccessful request, the window was completely blank after the request headers section; there simply was no more information available. If I manage to get the timing right again, I'll double-check.