The same thing happens to me on Chrome 20.0.1132.47 on Win7.
Perhaps the webpage is having trouble handling the load.
In any case I think you shouldn't be so quick to judge before you have even been able to read the actual content.
Of course we should be quick to judge it. It's a web page built on websockets that doesn't work, and it was linked for us to see it working on websockets.
Perhaps the webpage is having trouble handling the load. In any case I think you shouldn't be so quick to judge before you have even been able to read the actual content.