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
We would like onScroll as a prop on the TableBody.
🤔 Expected Behavior?
ability to pass onScroll in the table body and pass it on to the react element.
😯 Current Behavior
only aria label props get passed down.
💁 Possible Solution
include a list of allowed events in the filter props call to allow events to be subscribed.
🔦 Context
We have a complex table built on top of the react aria components table which does a sticky heading and sticky columns and our own virtualizer (due to this #7820).
We currently have to attach scroll events to the ref, but we would love to just be able to pass onScroll down to the TableBody.
We had some scroll syncing at one point in our React Spectrum implementation. I forget when we started S2 implementation if we would have needed to add something for that or if we had a want to handle it already. Could you open a discussion or issue about it?
Provide a general summary of the feature here
We would like onScroll as a prop on the TableBody.
🤔 Expected Behavior?
ability to pass onScroll in the table body and pass it on to the react element.
😯 Current Behavior
only aria label props get passed down.
💁 Possible Solution
include a list of allowed events in the filter props call to allow events to be subscribed.
🔦 Context
We have a complex table built on top of the react aria components table which does a sticky heading and sticky columns and our own virtualizer (due to this #7820).
We currently have to attach scroll events to the ref, but we would love to just be able to pass onScroll down to the TableBody.
@snowystinger mentioned to raise this as a seperate request: #7987 (comment)
We are happy to contribute a PR, just let us know if you are ok with this proposal.
💻 Examples
No response
🧢 Your Company/Team
Saxo Bank
🕷 Tracking Issue
No response
The text was updated successfully, but these errors were encountered: