-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
1px gaps and overlaps #916
Comments
I'm sorry to see you're having trouble with Isotope. Could you provide a reduced test case? See Submitting Issues in the contributing guidelines. |
Hi You can check it directly in the demo from your site http://codepen.io/desandro/pen/NqNBxy Just resize the window and you will see at some point images will start overlapping with 1px. |
Also having this problem, is this (#684) still the best solution? |
1px overlaps and 1px gaps are a result of rounding mismatches between displayed sizes of items and their positions on screen. There's no foolproof way to resolve them. If you prefer 1px gaps over 1px overlaps, you can size items with .grid-item {
width: 20%;
width: calc( 20% - 1px );
}
.grid-item--width2 {
width: 40%;
width: calc( 40% - 1px );
} Closing as |
I just added fixed width:320px; in my case and everything worked just fine. I have no need to make width dynamic, so it works well 👍 |
Enough issues have opened up on this issue, so I'm opening this one back up. I discovered that using fractional pixel values, i.e. Outlayer v2.1.1 has been released, with a fix for using float values. Isotope will get this fix in its next release. |
we build a issue for this bug:
this is a example for the vertical builder. |
⬆️ get-size 2.0.3, fizzy-ui-utils 2.0.7
Isotope v3.0.6 has been released with Outlayer upgraded to v2.1.1 |
Hi
I encounter a problem with isotope and bootstrap. On certain window size the images are overlapping with 1px ( from what i see when the width its xxx.5px )
Seems to be a common issue when the item width its sent in percents.
Is there any fix for it ?
Thanks a lot!
The text was updated successfully, but these errors were encountered: