Some buttons ("vote" and "accept" buttons) disappeared with Google Chrome 11. What is the reason?
For some reason, you'll have to clear your cache.
(This was asked earlier today, but then deleted by its author. Apparently clearing the cache helped for that user. Also, working in Incognito mode did not have these problems.)
Some more debugging info. Sorry for the huge post; hopefully it's just temporary :-) I still feel that Chrome is messing up, but maybe it helps investigating...
It seems that, when I get the issue, clearing the cache and not using a forced reload when things are fine, keeps me out of trouble. (If things are fine, then Command-R seems okay, but Command-Shift-R might break the cache, requiring one to clear it again.)
/content/js, not from the cookie-less
sstatic.netdomain. However, that also applies to, for example,
full-anon.jswhich shows no issues.
When things are fine, in incognito mode a Command-Shift-R refresh often does not refresh wmd.js (maybe just some optimization, but most others do get a full reload with 200 OK).
After clearing the cache, one needs to restart Chrome to ensure the cache is cleared for incognito mode too. (Maybe a new incognito session suffices.)
If all is fine, I get
For a normal Command-R refresh (here in incognito mode), when getting 304 Not Modified for
wmd.js, all is fine too:
But when things go bad, then for a normal Command-R refresh (here in incognito mode), when getting 304 Not Modified for
wmd.jsboth do not specify the content type, which seems fine to me:
When things have gone bad, for a forced Command-Shift-R refresh all resources are requested unconditionally, except for
wmd.js. While for all other resources
Pragma: no-cacheis requested, the request for
wmd.jsshows the odd
Range: bytes=17095-17095, and
If-None-Match: ..., the latter indicating a conditional refresh. Wireshark does not reveal an earlier request asking for (or getting) bytes 0-17093 or something like that. Note that the offsets for
Rangeshould be zero based, like
Range: 17904-17904for a length of 17905;
Range: 17905-17905is simply invalid here.
Just before things go bad,
chrome://view-http-cache/http://sstatic.net/js/wmd.js?v=c6b732291db9shows an odd
RESPONSE_INFO_TRUNCATED, while at the same time it then displays the page just fine, but only once. The Chromium source code claims: This bit is set if the request was cancelled before completion. That does not match what I am seeing in Wireshark, but I might be wrong. After that, as long as things are bad, the same result shows for the cached content:
But, 0x42c0 plus 7 bytes is in fact 17095... Wireshark shows nothing odd about the result. Like I see the expected size in
Content-encoded entity body (gzip): 17095 bytes -> 49186 bytes.
When all is fine, the cache shows exactly the same payload. The first lines, for the headers before the actual payload, vary just a bit. Probably different checksums for the different value for
Date: Sat, 07 May 2011 11:51:21 GMT 00000000: 52 01 00 00 01 88 00 00 24 36 35 82 44 01 2e 00 R.......$65.D... 00000010: c1 32 37 82 44 01 2e 00 17 01 00 00 48 54 54 50 .27.D.......HTTP
When things have gone bad, directly requesting http://sstatic.net/js/wmd.js?v=c6b732291db9 in the same incognito session gets me:
This webpage is not found
No webpage was found for the web address: http://sstatic.net/js/wmd.js?v=c6b732291db9
Error 6 (net::ERR_FILE_NOT_FOUND): The file or directory could not be found.
Changing the dummy query string works fine then. It gets me the same
Etag, but I doubt that would confuse Chrome. (If, for different SE sites, different dummy values for
?v=yield the same
Etag, then that should really be fine. Also, I've cleared my caches and tested using just a single site, assuming the Most Visited overview in a new Chrome tab does not actually make any requests, like Safari's Top Sites does... In fact:
chrome://view-http-cache/only shows the ones I expected.)
wmd.jsare loaded by
jquery.min.jsare loaded directly using things like
In July 2011, someone at xing.com reported a troublesome JS file that always shows this issue in the current Chrome 12 when loaded from their servers using HTTPS, but not when loaded from another server or when using HTTP. Changing the JS file to be a bit longer fixed the problem for them. See Chromium's issue 62712 for details.
(Of course, I am normally not using incognito mode. I've no extensions installed in Chrome.)
Yes, all the rich text controls disappeared for me today, and every answer I post I get the captcha. Something is rotten in Chrome land.
This is on the Mac, by the way -- don't know about other platforms yet.
Uncaught TypeError: Cannot call method 'initIfShown' of undefined d.d.extend._Deferred.f.resolveWith v d.support.ajax.d.ajaxTransport.send.c
All pointing to
- Ubuntu 11.04
- Google Chrome 11.0.696.57
No recent extension installations to blame.
Update: Gosh, the error message would help, wouldn't it?
pixel.quantserve.com/pixel;r=1341183499;fpan=0;fpa=P0-1145367131-1304363738348;ns=0;url=http%3A%2F%2Fstackoverflow.com%2Fquestions%2Fask;ref=http%3A%2F%2Fstackoverflow.com%2F;ce=1;je=1;sr=1280x1024x24;enc=n;ogl=;dst=1;et=1304710849521;tzo=240;a=p-c1rF4kxgLUzNc:-1Resource interpreted as Image but transferred with MIME type text/plain. stub.js:1 Uncaught TypeError: Cannot call method 'initIfShown' of undefined
This is only happening on Stack Overflow, as far as I can tell. I'm seeing the toolbar and preview right now on Meta Stack Overflow.
Request URL:http://sstatic.net/js/wmd.js?v=c6b732291db9 Request Method:GET Status Code:304 Not Modified Request Headers Accept:*/* Accept-Charset:ISO-8859-1,utf-8;q=0.7,*;q=0.3 Accept-Encoding:gzip,deflate,sdch Accept-Language:en-US,en;q=0.8 Connection:keep-alive Host:sstatic.net If-None-Match:"1b9f454caebcc1:0" Range:bytes=17095-17095 Referer:http://stackoverflow.com/questions/ask User-Agent:Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.57 Safari/534.24 Query String Parameters v:c6b732291db9 Response Headers Accept-Ranges:bytes Cache-Control:max-age=604800 Date:Fri, 06 May 2011 19:51:57 GMT ETag:"1b9f454caebcc1:0" Last-Modified:Fri, 06 May 2011 05:27:31 GMT
I am experiencing the very same issue on another website. I posted a new question on Stack Overflow to discuss it: Corrupt Google Chrome cache