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
Describe the bug
When using a responsive grid with grid items that have their widths defined in percentage, filterizr does not correctly calculate the width in pixels of each grid item.
Filterizr version
2.2.4 - Vanilla JS version
To Reproduce
I've created a codepen that illustrates the issue.
I've setup a basic grid with 25% width items
Then added a wrapper on the whole grid with a width (622px) that is not divisible by 4 without having decimals.
Normally the calculated width of each grid item in pixels should be 155.5px, but filterizr makes it 156px. I'm guessing it might be a rounding issue?
Result is that instead of displaying 4 items on one row, there are only 3.
Desktop (please complete the following information):
OS: OSX 10.14
Browser: Chrome
Version: 85
Additional context
I think it might be related to #33, although the issue is marked as fixed already in 2.2.0
The text was updated successfully, but these errors were encountered:
I have the same issue with Bootstrap columns. Initializing filterizr with a small negative value for gutterPixels (e.g. -1) seems to work around the bad calculation.
I have the same issue with Bootstrap columns. Initializing filterizr with a small negative value for gutterPixels (e.g. -1) seems to work around the bad calculation.
This fixed the problem. Thank you so much for the fix. 😍
Describe the bug
When using a responsive grid with grid items that have their widths defined in percentage, filterizr does not correctly calculate the width in pixels of each grid item.
Filterizr version
2.2.4 - Vanilla JS version
To Reproduce
I've created a codepen that illustrates the issue.
Desktop (please complete the following information):
Additional context
I think it might be related to #33, although the issue is marked as fixed already in 2.2.0
The text was updated successfully, but these errors were encountered: