Just curious, when I came here first, I was very thankful that whoever had written the CSS had apparently taken care to not produce errors. But after some recent updates, my console is now flooded with error messages. Some of them very simple to fix, like using the wrong type of commentaries for CSS.
I know this is probably minor to most people, but it's really one of the fine details that I'd appreciate. These are just the errors I get from global.css, there are more in skin.css (mostly filter errors), but you get the idea.
global.css
Lines 6,1575,1795: Invalid CSS comment with // instead of /* */
Lines 43,132,969,973,977: IE only behaviour served to all browsers
Line 52: Semicolon missing
Lines 2642,2647,2648,2653: Comment inside CSS with "#".
Line 2469: Invalid CSS property resize (don't know that one, could be MSIE only)

You care about CSS? I see those errors in FF (if I look at the console), but I don't care.

It's just a very little annoyance. But if it can be avoided so easily with conditional comments and the correct comment directives, why put up with it?

Because the average person wouldn't know the difference. Only coders and web designers of varying skill would know!

But this is GoG! You don't expect to find average persons here, do you? ;)

Depends. An average person wouldn't buy Redneck Rampage anyway.

If something is worth doing; it's worth doing right. And there too few companies that ever bother to try and do things right when it comes to web =(. But at least GOG aren't claiming to use valid code/css when they aren't.

How do you know I bought RR?

Does it happen all the time in the forums? I guess that's Opera 9.6, right? I'll try it, maybe I can find the root of the problem.

Yep, Opera 9.6
And yes, it happens all the time, since the last updat (add of links to youtube, facebook, twitter).
Oh and thanks :D

Found it! (after a really annoying battle with Opera's developer tools). I'm not sure why yet, but the new icon after "Spread the word" is causing it. Sadly, Opera's tools are really a bitch to use, so it'll take me a second to actually figure out what's happening here.
OK, apparently, the definition for class stw_new is thoroughly messed up, including bogus values for anything that has to do with height and positioning. Apparently the code is meant to emulate inline-block, but it causes undefined behaviour in pretty much every browser.
Update: Filed an issue on this.

Wild guess.

I'm using the 64bit build of IE7 and haven't seen that "done but with errors on the page" thing. It is something that could give a bad impression though, someone comes here seeing good old games for sale cheap with no drm and they also see a website error they might be more likely to go elsewhere thinking it must be too good to be true

Don't worry about that. This is not the kind of error that is shown with an error message (only script errors do that on IE and these are style errors). It's just that Firefox quietly logs them to the error console... which is not shown to users normally, unless they enable it under Tools/Error Console. It's really not critical, just a bit annoying if you have that thing open for other purposes and see the error messages running by. It also slows Firefox down a bit (if the console is enabled).