Rows in <List> unmount and then mount when they leave the active window
See original GitHub issueThanks for the awesome library!
I noticed some strange behavior with the List
related to the overscanRowCount
setting. Let’s say there are 10 rows visible and overscanRowCount
is set 10. When I scroll the list such that a row leaves the visible region, but is still within the overscan radius, the component is unmounted and then instantly re-rendered. This is an issue since it causes unnecessary re-renders and resets the local state of the components as they leave the screen.
If this is indeed a bug, and not expected behavior, I’d be happy to code up a minimal reproduction and help work toward a fix!
Thanks!
Issue Analytics
- State:
- Created 7 years ago
- Reactions:1
- Comments:9 (7 by maintainers)
Top Results From Across the Web
How to keep React component state between mount/unmount?
This seems to be the way to go for me because I can create a mutable object and pass it as props, then...
Read more >Mount or unmount existing volumes in the NAS namespace
A volume must be mounted on the NAS namespace before you can configure NAS client access to data contained in the storage virtual...
Read more >List Unmounted Volume #s in batch with Diskpart or WMI
Hello, I need to create a Win7 Console batch that lists only unmounted volume "Numbers & Labels (if any)" for all or a...
Read more >DISM Image Management Command-Line Options
Deployment Image Servicing and Management (DISM.exe) mounts a Windows image (.wim) file or virtual hard disk (.vhd or .vhdx) for servicing.
Read more >Mounting file shares on Compute Engine clients | Filestore
In the Google Cloud console, go to the VM Instances page. · Locate the Linux VM you want to use as a client,...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
True, it could, but every configurable property has a cost (in runtime complexity, code management complexity, API complexity/understandability, etc.)
In this case, I’m not really convinced that the cost is justified. I could change my mind though. 😃
Limiting the total number of rows rendered. This matters more when there are overscanned rows and columns b’c the number grows faster.