You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Looking at dgrid's test/complex_column.html page in Chrome 58 some horizontal row borders are missing. This is due to the element's height being set to 100%, which doesn't make sense since it doesn't have an explicitly sized parent.
Removing the height rule allows the element to vertically size correctly and the bottom border does not get cut off.
The text was updated successfully, but these errors were encountered:
msssk
added a commit
to msssk/dgrid
that referenced
this issue
May 8, 2017
Here are some images to clarify the problem (which still exists in Chrome as of version 79):
In the 3rd visible row, the cells in columns 1 and 2, with the values "note" and "false", have no border below them:
The same row when hovered makes the entire row dimensions clear:
Removing the 100% height rule for the column set results in the borders being displayed along the bottom of the cells, but the cells do not expand vertically to fill the row, which I think is undesirable:
The following rule will reduce the height of the cell so that its border is not clipped:
This almost works, but the bottom border can end up misaligned with the bottom border on the adjacent cell.
Column Sets allow you to create some complicated structures that are rendered inconsistently across browsers. I'm not sure how to fix this, but we should at least record it as a known issue, with some information on possible solutions, perhaps in the Column Set documentation.
Looking at dgrid's
test/complex_column.html
page in Chrome 58 some horizontal row borders are missing. This is due to the element's height being set to100%
, which doesn't make sense since it doesn't have an explicitly sized parent.Removing the height rule allows the element to vertically size correctly and the bottom border does not get cut off.
The text was updated successfully, but these errors were encountered: