Solo Grid Margin Issue #6685
Comments
To confirm: here's the simplified version: http://jsbin.com/uLIxoGU/3 (removed all unrelated CSS and JavaScript). The same with 1.3.2 does not show the pb: http://jsbin.com/uLIxoGU/2 This seems to be due to @uGoMobi This is the commit: 71448a6#diff-73214b44ef91605e3cf8574cad62e419R54 |
Thanks for digging into this issue and finding the commit for traceability. I know there are other selectors using these margin rules: Full Selector Stack: As long as there are no negative implications to removing the .ui-grid-solo > [class*="ui-"] selector, I vote to to remove it, its addition may have been a mistake. |
I will fix that demo and revert 71448a6. We don't make changes in the framework at the moment because we are on RC and I don't find this bug critical enough to release another RC. Until 1.4.1 it can be solved by negating the margin in your custom CSS. See http://jsbin.com/AKOmUxa/77/edit. Sorry for the inconvenience! |
…block-a This is the correct fix for #6643. The changes from commit 71448a6 have to be reverted. See #6685 (comment) 2
…block-a This is the correct fix for #6643. The changes from commit 71448a6 have to be reverted. See #6685 (comment) 2
When fixing this we have to test navbars with one button (see #6775) |
@uGoMobi @uGoMobi #6775 shows the problem with one and multiples button. Even with 6 button you still get a problem because of the margin-right: -4px; Disregarding any regression, removing those 2 fix the problem: /* fixes gaps caused by subpixel problem */ [class_="ui-block-"] > .ui-btn, |
When using a solo grid you get extra margin on either end causing it to have a slightly off center layout.
I have noticed this in 1.4.0 rc1, though it could be an issue in past versions.
JSBIN Here:
http://jsbin.com/OXElOlu/1/
The text was updated successfully, but these errors were encountered: