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
Hi! First off, thank you so much for viewport level virtual scroll, this is immensely helpful. I think I found a resize issue when using table virtualizer and TableLoadMoreItem where the load more item sentinel is not resizing when the page width is modified, which leads to the sentinel not being centered on the screen when shrinking the window. If you inspect the DOM when resizing, you'll see that the virtual header component DOES resize the width but the parent table doesn't nor does the TableLoadMore sentinel inside it...Instead it remains the largest width (never shrinks)
🤔 Expected Behavior?
I expect the sentinel to be affected by the width of the container and resize to match the width of the container
😯 Current Behavior
The sentinel (and parent table element) do not appear to be affected by resize events. maybe the parent isn't resizing because it sees a child element with such a large width and isn't resizing because of that.
I added a long sleep for each load so you can see the sentinel.
Notice how the load more sentinel doesn't remain centered in table (it's because it's width is never adjusted to be the new width of the parent container)
I actually discovered this because of a different side affect of the sentinel not resizing during development...where it was causing a weird overflox x scroll, after resizing a table. The repro above doesn't have this issue, but it stems from the same problem. If I remove the sentinel from my app's table, i no longer have this weird overflow x issue. Video if you're curious
Provide a general summary of the issue here
Hi! First off, thank you so much for viewport level virtual scroll, this is immensely helpful. I think I found a resize issue when using table virtualizer and
TableLoadMoreItemwhere the load more item sentinel is not resizing when the page width is modified, which leads to the sentinel not being centered on the screen when shrinking the window. If you inspect the DOM when resizing, you'll see that the virtual header component DOES resize thewidthbut the parent table doesn't nor does the TableLoadMore sentinel inside it...Instead it remains the largest width (never shrinks)🤔 Expected Behavior?
I expect the sentinel to be affected by the width of the container and resize to match the width of the container
😯 Current Behavior
The sentinel (and parent table element) do not appear to be affected by resize events. maybe the parent isn't resizing because it sees a child element with such a large width and isn't resizing because of that.
💁 Possible Solution
No response
🔦 Context
No response
🖥️ Steps to Reproduce
Video Demo of the Stackblitz above:
Screen.Recording.2026-04-16.at.9.30.13.PM.mov
I took the https://react-aria.adobe.com/Table#asynchronous-loading example and wrapped Virtualizer around it
I actually discovered this because of a different side affect of the sentinel not resizing during development...where it was causing a weird overflox x scroll, after resizing a table. The repro above doesn't have this issue, but it stems from the same problem. If I remove the sentinel from my app's table, i no longer have this weird overflow x issue. Video if you're curious
Screen.Recording.2026-04-16.at.9.42.34.PM.mov
Let me know if you need anything else! Thanks!
Version
1.17.0
What browsers are you seeing the problem on?
Chrome
If other, please specify.
No response
What operating system are you using?
Mac OS
🧢 Your Company/Team
No response
🕷 Tracking Issue
No response