>>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 :(
>
>You're doing the same thing again. The .CSS is perfectly valid. It may cause the grid to display incorrectly when there's no data but removing it, just as when you adjusted the other code, is simply hiding the symptom and not addressing the problem.
>
>It you keep doing this you will end up with a form that displays perfectly without data - which if probably what you want since you don't have any :-}

The site.css file already had .gridStyle defined. That was an extra addition close to the end (defining this class again). My colleague was also experiencing some weird ng-grid behavior in another form and that was his attempt at fixing.