Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 158 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

I'm getting the following js errors per browser, on Win7:

  • Firefox 9.01

    h.end is undefined

  • Chrome 16.0.912.77 m

    Uncaught TypeError: Cannot read property '0' of undefined

  • IE

    SCRIPT5007: Unable to get value of the property '0': object is null or undefined


What appears to be broken is the background flash when following a permalink to an answer. It works on MSO, but it's broken on Stack Overflow and Programmers.SE, the background just stays orange.

share|improve this question
We have just purged our CDN - can you try it again and let us know if you are having the same result? – Geoff Dalgas Jan 31 '12 at 5:21
@GeoffDalgas Nope, same errors. But I'm still getting stub.js?v=2bc4ea846933, and it's different from the current version at the end, var c={}})(jQuery); vs var c={transparent:[255,255,255]}})(jQuery); respectively. By current, I mean what I get for ?v=blahblahblah_helloworld!... – Yannis Jan 31 '12 at 5:48
can you tell us what node you are hitting: – Geoff Dalgas Jan 31 '12 at 5:55
@GeoffDalgas NetDNA Amsterdam Datacenter – Yannis Jan 31 '12 at 5:55
we have just purged all instances of stub.js - could you try again? – Geoff Dalgas Jan 31 '12 at 6:18
@GeoffDalgas I'm still seeing that (Firefox 9.01 and Chrome 17/Linux) - same NetDNA datacenter as Yannis. Cleared all caches. – Mat Jan 31 '12 at 6:59
It appears that we have an issue with purging in our Amsterdam datacenter - I'll get back with an official response – Geoff Dalgas Jan 31 '12 at 7:35
@GeoffDalgas Everything back to normal, thanks! – Yannis Jan 31 '12 at 17:12
up vote 3 down vote accepted

Something seems to be broken with the caching in the Amsterdam CDN node. It's still broken (I can see it as I'm hitting Amsterdam as well); I've contacted the CDN support about this.

But the file just got a new cache breaker, which forced the CDN to re-download a file, and thus you're getting the correct JavaScript now, so it works again.

share|improve this answer

It works just fine for me with Google Chrome. Maybe a local cache issue or something?

share|improve this answer

You must log in to answer this question.

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