Issue with Google Chrome
- This topic has 6 replies, 3 voices, and was last updated Feb 28, 2014 at 4:14 pm by
.
-
Posts
-
Guys we’re having an issue with Google Chrome right now, where it is losing the CSS style sheet that dictates what the site looks like, and thus also losing the site contents. This not a problem in Internet Explorer, Firefox, Safari or on any mobile browser to the best of my knowledge. It seems to be related to Chrome’s most recent update.
I’ve submitted bug reports and I am making as much noise as possible on the Google product forums. It’s a widespread issue with multiple WordPress users complaining of the same thing, and not a coding issue with this site per se, so there’s nothing I can do to fix it.
Thanks,
ZachHmm. It might take you a while of browsing, Ian, because you need to generate a 304 server response, which is what it sends when everything is cached on your local box and nothing has changed. Here’s my Google Chrome bug report with screenshots from my work PC, but it’s happening on Chrome in OSx as well.
Well, I downloaded Google Chrome Canary, which is their next, not-yet-released build, and, knock on wood, the problem seems to have been resolved. Which may be why no one has responded to my bug fix notice.
Zach
It is definitely fixed; I just watched it barf on a 302 response and then force a 200 response (re-downloading the files) out of the server. It happened in a split second.
This issue seems to be due to a non-standards-compliant response from some http servers. I think the issue is that no browser has ever really paid attention to the meta data on a 302 response page (which we as web designers can’t even see or alter unless we are running our own servers with access to Apache’s back end, which no one on a shared or semi-dedicated package like this site has).
So suddenly Chrome up and decided to be ultra standards compliant and thus exposed all the servers which had never particularly bothered to make sure the 302 page reflected a proper “content-type” setting.
All super annoying. “Content-type” is one of those stupid sub-classification tags that serves only to satisfy the code programmers’ need to list all possible variables, when 99.99% of the time the type is either html or (and this is why Chrome is barfing), css.
When you code a site like this, you come to believe that half the time the people who invent these code languages are just classifiers, classic “splitters” instead of “lumpers”. They want every little image link to have an “alt=” definition, etc. Just look how many variables you can optionally set for a simple < a href = > link:
http://www.w3schools.com/tags/tag_a.asp
Who cares? A link just needs to point the browser to a url unless you’re trying to do something crazy like open it in a specific size of window. Crap like this drives me crazy–it is the tyranny of the nerd.
Zach
Zack,
Even the nerds want to be noticed, the “see what I made the entire internet do today?” mentality. Wonder if they toast themselves with milk and cookies tonight.
- You must be logged in to reply to this topic.