Houston, we have a problem.
That was a bit of silly error in our javascript. The next build has the fix.
