-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue with Collection scrolling when data is loaded async #525
Comments
Thank you for the Plnkr and the detailed bug description. Looks like this bug can be reproduced on the official site as well: https://bvaughn.github.io/react-virtualized/#/components/Collection
The problem seems to be that the |
Interesting... these lines are forcefully turning off scrollbars if the content is not tall or wide enough to require scrolling. It seems that once I've set a value for This seems like a bug outside of react-virtualized. I can fix it in react-virtualized though by making |
It seems that after specifying an overflowX (or overflowY) style then subsequent overflow styles get dropped. This causes the broken behavior originally reported in #525. This commit resolves that issue.
Fixed with b5b8e29. Will go out in a release sometime in the next couple of days. In the meanwhile you should be able to work around this on your end by passing a <Collection
{...props}
style={{
overflowX: 'auto',
overflowY: 'auto'
}}
/> |
I've captured this bug with a small Plnkr and reported it here: facebook/react/issues/8689 |
The underlying bug actually impacts all shorthand CSS properties. Turns out that shorthand properties aren't [fully?] supported by React due to how the style updates are currently done. I was unaware of this. Either way, it's been fixed in react-virtualized for now and the fix will roll out with the next release. |
Superb, thanks for that. Just been reading up and I don't feel so bad about not solving it myself now 👍 Build failing btw |
https://plnkr.co/edit/81aoXFH8mkZhoxaKib2o
So first off, I've setup a plunker as requested. This is a snippet of what we are/were planning to use in production.
As it stands, the grid works as desired. When we started using real data, we came across a big problem.
To see the issue, on script.jsx - line 45, if you comment out the initial "this.populate()" then you can see the entire grid / page scrolling rather than just the items as desired.
At the moment I am cheating by seeding the grid with initial data but I'd like to not do this.
Thanks.
The text was updated successfully, but these errors were encountered: