Skip to content
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

Rows rendered outside of view #807

Closed
nifgraup opened this issue Sep 8, 2017 · 5 comments
Closed

Rows rendered outside of view #807

nifgraup opened this issue Sep 8, 2017 · 5 comments

Comments

@nifgraup
Copy link
Contributor

nifgraup commented Sep 8, 2017

Steps to reproduce

What happens
The list is just white. Everything is fine when "Num rows" is set to 10000. The DOM nodes are positioned outside of the list. It's possible to bypass this issue by making DEFAULT_MAX_SCROLL_SIZE very large.

@bvaughn
Copy link
Owner

bvaughn commented Sep 8, 2017

At a glance, I think this maybe indicates a bug with cached styles and scaling. RV handles resized rows properly in non-scaling case (eg 1000 rows) but needs a nudge to properly reset itself when things change from non-scaling to scaling (or maybe when scaling changes from one scale to another, note sure).

FWIW when I say "scaling" I'm referring to this which is done by this.

Help is welcome on this issue. My guess is that it's kind of an edge-case one though.

@avranju
Copy link

avranju commented Nov 21, 2017

I am seeing a similar behavior with a table component inside an AutoSizer. A new row gets dynamically added about twice a second and after about 16000 rows I see the screen going blank with every update. If I scroll up or down a bit it comes back and then blanks out when the next row is added.

@nifgraup
Copy link
Contributor Author

I can not reproduce anymore.

@nifgraup
Copy link
Contributor Author

nifgraup commented Apr 5, 2019

Still an issue, I didn't test properly when closing.

@nifgraup nifgraup reopened this Apr 5, 2019
nifgraup added a commit to nifgraup/react-virtualized that referenced this issue Apr 8, 2019
@nifgraup
Copy link
Contributor Author

nifgraup commented Apr 8, 2019

This used to work, but detection of Chromium based browsers broke when chrome.webstore was removed around v71. Submitted pull request: #1355

wuweiweiwu pushed a commit that referenced this issue Jul 25, 2019
Fixed reintroduction of #807
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants