Opening expandable grid causes parent grid to collapse when setting width to parent grid columns

[tanak]

Opening expandable grid causes parent grid to collapse when setting width to parent grid columns.

I checked this with Chrome, Firefox and IE on Windows.

This is my plunker.
http://plnkr.co/edit/8phKFI0hzfmN7lWK9zMe?p=preview

[PaulL1]

When I used your plunker as-is, it didn't do anything for me, and returned errors in attempting to return the rowTemplate. When I put the rowTemplate inline to avoid this issue, the breakage doesn't occur: http://plnkr.co/edit/DHXXQiQ5tJBNye1l7zQQ?p=preview

Is there a reason you need to retrieve your rowTemplate dynamically?

[tanak]

Thank you for checking. I also modified the plunker.

I checked on Chrome in Mac again and found that the problem doesn't occur in a small screen.
It seems that the breakage occurs with larger screen.

Could you use a separate window for preview and check again?

[PaulL1]

OK, now I see it. It isn't breaking the formatting so much, rather what's happened is that the grid is wide enough to fit multiple rows onto a single row (the expanded section is much wider than the core grid). If you define the core columns as being wider it doesn't happen (e.g. if you change the widths to 300 each). However, if you don't know how wide the screen is then this won't work. Setting the widths in % might work (if they always add to 100% or thereabouts), but if you let users resize their own columns this could still be a problem.

I presume that means something is messing up the css, as it only does it below the sub-grid, but I can't see what. @jpuri - any ideas?

[PaulL1]

This appears resolved on the plunker - could you confirm?

[tanak]

I checked with v3.0.0-rc.20-6520046, but expandable seems not to be working with this version.

I also checked the tutorial page, and the result was the same.
http://ui-grid.info/docs/#/tutorial/306_expandable_grid

[PaulL1]

Hmm. That seems to have broken overnight. It looks to be fonts, not code - when I check out the code and build and run it, it's fine locally. It will no doubt come right next time someone pushes something.

[PaulL1]

OK, the fonts have been fixed on this for some time, and the plunker no longer exhibits the poor behaviour. Closing, can you re-raise if this issue recurs?