In Google Chrome
>> goto settings
>> search for cache
>> clear browsing data
>> check cached images and files (the past hour / day)
>> clear browsing data
and goto your webpage and press "Ctrl + r"
Hope this solves your issue Cheers.
Answer from Shyam on Stack OverflowIn Google Chrome
>> goto settings
>> search for cache
>> clear browsing data
>> check cached images and files (the past hour / day)
>> clear browsing data
and goto your webpage and press "Ctrl + r"
Hope this solves your issue Cheers.
Make sure that your CSS and HTM/HTML files use the same encoding !
If your HTM/HTML files are encoded as UNICODE, your stylesheet has to be as well.
IE and Edge are not fussy : stylesheets are rendered regardless of the encodings. But Chrome is totally intolerant of unmatched encodings.
I tried every solution/suggestion i could find all over the Internet before i noticed, in my text editor, that i was using different encodings. Once I saved the stylesheets with the same encoding used for the web pages, the problem disappeared.
Videos
This is a very weird issue. I have 2 Chrome profiles, one for work and another one for everyday use. The everyday one works just fine, but the other one seems to fail loading some of the css styles of multiple pages. For example, in Gmail the checkboxes to select each email in my inbox are not visible, I can try and click where it is supposed to be and it works though. These three for example are selected, when you hover them that little oval pops up for some reason.
Also, there are some elements that are supposed to be displayed in line but end up being rendered one over the other, messing up texts and images.
Another error I just found, the search icon in gmail is super small compared to every other element:
Does anyone know what is going on? Just clarify, this doesn't happend with my other Chrome profile. Not only that, if I try using this same profile on another device, the errors are still there.
The browser is outputting javascript errors, if you check the code, you're calling jQuery's document ready before the script is loaded, as it says, "$ is not defined".
After fixing the existing javascript error, it should load correctly.
I am seeing the same behavior on one of our own sites and started looking for a cause. The only conclusion I could come up with for now is that it is caused by the Mime Type of your stylesheet. This conclusion is supported by the behavior on our side.
Update: There are three ways in which Chrome seems to load the CSS file:
- As a fresh request, no cached version available, our server returns
HTTP 200 OK, with content-typetext/css. This works fine. - From the cache, without consulting the server. Chrome has cached content-type
text/css. This works fine. - As a request with a cached version available. Our server returns
HTTP 304 Not Modified, with content-typetext/plain. This does not work.
Do you have HTTPS everywhere + Adblock installed? If so, I've found that clicking through google search results will often produce this behavior when the main site has no, or limited https support.
I notice the same behavior, with those extensions, when I search for and click through an XKCD comic, for example.
Temporarily disabling https everywhere, or re-entering the URL without https seems to fix it for me.
Maybe a caching problem on your side. Can you try "Shift+Ctrl+R"?