>>>Why is it you just don't listen to what Viv, Greg and others have been telling you for months. You cannot just grab something with an error in it and start twiddling bits, changing this and changing that until it works. Then you have situations exactly like this. Everyday, there is something else wrong. You say, "but I didn't change anything", yes you did. YOU NEED TO DEBUG IT AND FIND THE CAUSE OF THE ERROR. Then you fix the cause not stick bandaids everywhere till you think its okay. Like Viv said, I'm glad I don't have to use or maintain your code. What a nightmare.
>>
>>How will you explain the fact that everything is working perfectly for another developer who showed that story today?
>>
>>I haven't asked other people yet to verify but I suspect something is changing in my particular environment (may be even a virus).
>
>When you're testing make sure you start up the browser in private/incognito mode. Browsers will sometimes be really nasty about caching things you don't expect to be cached (so changes you made may not take effect immediately). In private mode you can just close the browser and open a new private instance and be sure it's not still caching something unexpectedly.

Ok, I think I found the reason for bad behavior. Most likely my colleague didn't download all the latest stuff when he was demoing my story or his site.css was cached.

In one of my colleagues changes I see new code added to site.css:

.gridStyle {
    width: auto; 
    height: 125px;

Most likely this is what is messing my grid now. I am going to comment it out locally and re-test.

UPDATE. It was indeed the cause of this behavior. Cost me a couple of hours :(