[sabret00the]

"You don't have Javascript enabled" so let's show you just how badly we can make rendered HTML look. Great work there Quartz!

As for the article, it's an article about racing, not sure why they mentioned football or the metric system at all, but to mention it in the context they have, they should've called it by it's proper name "Football" and then perhaps added "Soccer" in brackets.

[sergiotapia]

If you don't have Javascript enabled that's a conscious decision you've made, fully aware of what the tradeoff is.

Either turn it on for websites you want to read properly, or just accept the fact that it's 2013 and the vast majority of websites use it.

[errnoh]

I do have JS enabled but still run into problems. Probably some script blocking plugin that's causing them but the cause doesn't really matter, what does is the fact that it's preventing one from reading the article.

There's really no reason at all to obfuscate text based information in such way unless you want to display ads or track the user. It even shows the actual article behind the loading screen but you can't read the article itself since the loading never finishes. That's just bad design.

It's not the first time I've had to open lynx in order to read an article that's behind some javascript nonsense. (note: the text data is fine, it's actually only broken on modern browsers which actually handle js)

[sergiotapia]

shrug

What can I tell you? If you are using a script blocker this is what you get in the current landscape. There really isn't a reason why text should be mangled without javascript, but that's just the way it is with some sites.

[pooriaazimi]

Believe me, their "badly-rendered HTML" is sooooo much better than the stupid, stupid "thing" they show you when JS is enabled...

[buro9]

Chrome F12... then delete the overlay and enjoy the article.

[zalew]

wow, they are worst 'js for reading text' offenders than blogspot.