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
v2.0.0-beta.4 (using Bootstrap 5.0.2) renders a single column. 20 cards were present, all in one column and regardless of card width. neither mention of change in documentation, nor property(s) necessary to achieve multiple columns. Docs do show an example of a single column, implying a change to CardColumn (singular column) functionality, which if intentional warrants a Component rename and I propose a multiple-column CardColumns option.
Expectation
v1.6.1 (Bootstrap 4.6.0) renders 3 columns by default (possibility: card width possibly a factor for column number). 20 cards were also present, divided between the three columns. Documentation does show an example of 3 columns.
Fwiw, the recommended approach to use Masonry does not work out of the box with react. Columns are equal in height to the largest card in the row. See attached. The component should be removed from docs for sure because it was removed from bootstrap but I'm wondering what the alternative is for react-bootstrap users?
The Bug
Result
v2.0.0-beta.4 (using Bootstrap 5.0.2) renders a single column. 20 cards were present, all in one column and regardless of card width. neither mention of change in documentation, nor property(s) necessary to achieve multiple columns. Docs do show an example of a single column, implying a change to CardColumn (singular column) functionality, which if intentional warrants a Component rename and I propose a multiple-column CardColumns option.
Expectation
v1.6.1 (Bootstrap 4.6.0) renders 3 columns by default (possibility: card width possibly a factor for column number). 20 cards were also present, divided between the three columns. Documentation does show an example of 3 columns.
To Reproduce
Steps to reproduce the behavior:
Screenshots
not working:
working:
Environment
The text was updated successfully, but these errors were encountered: