I suddenly find myself unable to add comments on Stack Overflow when I'm using Chrome version 9.0.597.98.

I have sufficient reputation to comment; I can comment when I log in using Internet Explorer 8; it works fine in Firefox 3.6.13, too.

What setting have I changed or what library am I missing to break this functionality?


I started the developer tools in Google Chrome and looked at the error logs. Here are two errors that might be germane:

Uncaught ReferenceError: $ is not defined - master.min.js
Failed to load resource - jquery.min.js

I'm all set - shift-F5 did the trick. Thanks so much to all who answered.

  • testing. I'm using Chrome 9.0.597.102. edit: no repro. – Jin Feb 13 '11 at 4:08
  • 1
    It would help a lot if you described at what point in the process it breaks down? – Nicole Feb 13 '11 at 17:20
  • 1
    I'm going to move this to SO because this functionality is appearing on all sites. For what it's worth they don't support beta versions officially, so see if you can reproduce this in Chrome 8. – Josh K Feb 14 '11 at 14:06
  • I had a similar issue happen to me yesterday on SO in firefox. Suddenly I lost the ability to vote, comment, and view vote totals. In the error console I could see a couple of JS errors (gauth not defined or something similar to that). Clearing my browser cache fixed it. I assume some update must have happenned that was incompatible with a cached script file I already had. – Martin Smith Feb 14 '11 at 14:18
  • Happened to me today right here on Meta - all JS related stuff stopped working and Chrome console showed some really bizarre errors.. pity I didn't copied them! – Shadow Wizard is Ear For You Feb 14 '11 at 14:24
  • @Josh - Chrome 9.0.597.98 is the officially released version. – ChrisF Feb 14 '11 at 14:25

Try shift-F5.

|improve this answer|||||
  • On a windows system shift-F4 also does a good job. – stacker Feb 15 '11 at 22:12
  • This took care of it. Thank you so much. – duffymo Feb 24 '11 at 3:10

You didn't do anything, it's temporary glitch that happened to me as well (and to others judging from the comments) as result of client side script error in one of the external resources.

If it happens again go to Tools --> JavaScript Console and copy the exact error so the moderators will have something to work with. :)

Unless it's permanent behavior that you're still having??

|improve this answer|||||

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .