Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 157 Stack Exchange communities.

What is meta?
Here's how it works:
  1. Any Stack Exchange user can ask a question
  2. The community provides support, votes on ideas, and reports bugs
  3. Your voice helps shape the way Stack Exchange operates

When a page has loaded the first time, sometimes links like edit, add comment, share, flag do not work. I have been having noticing this for quite some time now.

On reloading the page, either refresh or clicking on the post title however, they seem to work.

But then, I noticed this not only while at work but also at home.

  • First, I thought it would have something to do with caching of scripts etc. So I even tried clearing my cache.

  • And this is not for deleted/closed questions, I verified.

  • There are no errors in my browser console either.

Although, I know it might not be a well-documented bug because I use only Chrome (v21.0.1180.79 m), I thought it should still be worth posting.

UPDATE :

This was the error

Uncaught TypeError: Property '$' of object [object Window] is not a function 

in the file cdn.sstatic.net/js/full.js?v=c60de8021771:24

enter image description here

I'm guessing something hasn't loaded the first time? Still digging into it.

share|improve this question
    
I use chrome and do not have that problems. – juergen d Aug 21 '12 at 12:13
    
I forgot to ask if it's just me or has anybody else also come across this glitch.(if it even is one) – Robin Maben Aug 21 '12 at 12:16
    
Maybe it's a connection issue and the scripts are not completely loading? Did you check the network tab on chrome tools? – bfavaretto Aug 21 '12 at 13:24
    
@bfavaretto: The network tab should already be open for it to show the requests being made. :/ – Robin Maben Aug 21 '12 at 13:31
    
What version of Chrome? – Time Traveling Bobby Aug 21 '12 at 13:31
    
@WaffelizedBobby: The latest - 21.0.1180.79 m. Updated answer too. – Robin Maben Aug 21 '12 at 13:33
    
Might be a Chrome bug. – Time Traveling Bobby Aug 21 '12 at 13:36
    
@WaffelizedBobby: See my update. I was able to reproduce this. – Robin Maben Aug 21 '12 at 14:56

You must log in to answer this question.

Browse other questions tagged .