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
I've noticed an issue on the most recent version (1.20.2) where the allotment component doesn't seem to initially paint at the full width of its content. See the video below of the storybook where I am repeatedly pressing the "remount" button. This happens quite fast, but if you pay close attention, you'll see the width of the grey container is initially quite small, then quickly "snaps" into its full-size.
It's almost as if JS is being used to calculate the width of the content, (which I believe will always be 0 in first render), then sets the width of the allotment panes based on that. Is this fixable? It begins to become fairly noticeable on views where there is a lot of markup to render.
Screen.Recording.2024-09-26.at.3.26.11.PM.mov
The text was updated successfully, but these errors were encountered:
I've noticed an issue on the most recent version (
1.20.2
) where the allotment component doesn't seem to initially paint at the full width of its content. See the video below of the storybook where I am repeatedly pressing the "remount" button. This happens quite fast, but if you pay close attention, you'll see the width of the grey container is initially quite small, then quickly "snaps" into its full-size.It's almost as if JS is being used to calculate the width of the content, (which I believe will always be
0
in first render), then sets the width of the allotment panes based on that. Is this fixable? It begins to become fairly noticeable on views where there is a lot of markup to render.Screen.Recording.2024-09-26.at.3.26.11.PM.mov
The text was updated successfully, but these errors were encountered: