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
``While trying to use a "custom" react component that handles grid layout, the docs state to use the display: contents attr if adding a "wrapper" around the child creates layout woes. In doing so, it still appears to mess with the layout AND does not animate.
This yields an 11 column grid with the first column starting in position 2. In fact, what happens is each column subsequently uses only 1 column worth of available space even when the specified span at the lg breakpoint is set to 3.
what am i missing?
The text was updated successfully, but these errors were encountered:
Can you setup a codesandbox or something similar to help debug? Since you are using some custom React components here it is difficult to determine what exactly the issue might be. Another way to help might be to copy the generated HTML into a Codepen or sandbox.
A few questions that might help:
Why do you need to wrap the Column element in a div? Can you map over the Column elements and put the key directly on them?
Can you avoid using the custom layout elements and just use className and regular CSS? That way you might be able to avoid needing wrapping elements and the grid styles can go directly on the element generated by the XyzTransitionGroup.
``While trying to use a "custom" react component that handles grid layout, the docs state to use the
display: contents
attr if adding a "wrapper" around the child creates layout woes. In doing so, it still appears to mess with the layout AND does not animate.Example:
This yields an 11 column grid with the first column starting in position
2
. In fact, what happens is each column subsequently uses only1
column worth of available space even when the specifiedspan
at thelg
breakpoint is set to3
.what am i missing?
The text was updated successfully, but these errors were encountered: