[BUG] List is not being rendered when initialTopMostItemIndex is specified
See original GitHub issueDescribe the bug I think this is a bug introduce in 1a230ef78d7003c0340ac253f3232d420ca9e23a. In version 2.2.1, the list is not being rendered sometimes. Writing is hard, let’s attach some gif
Behavior in v2.2.0 (Expected behavior)

Behavior in v2.2.1 (Unexpected behavior)

Reproduction https://codesandbox.io/s/gallant-wescoff-n50s4?file=/src/App.js Please change the version in package.json to test the behavior.
To Reproduce Steps to reproduce the behavior: Re-run the following steps on version 2.2.1 and 2.2.0
- Change react-virtuoso version to xxx
- Refresh, click on
Change item set - Observe the result
Expected behavior List should be rendered like how it is in v2.2.0
Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:21 (10 by maintainers)
Top Results From Across the Web
Start from a certain item - React Virtuoso
Start from a certain item. The initialTopMostItemIndex property changes the initial location of the list to display the item at the specified index....
Read more >A Taxonomy of HTML5 Canvas Bugs - arXiv
The HTML5 <canvas> allows the rendering of high quality graphics in web applications. ... specific bug type for a given bug report. However,...
Read more >React key attribute: best practices for performant lists
The id-based behaviour is correct and performant: items are recognized accurately, and every item is memoised, so no component is re-rendered.
Read more >react-virtuoso - Bountysource
I'm currently using the VirtuosoGrid component to render a long list of items in a grid, using CSS grid, and it's working great....
Read more >React keys for non-list elements? - Stack Overflow
Here jsfiddle.net/bqvod1n9 gives error for keys in the console, but when render doesn't have components as an array jsfiddle.net/z8vqt9Lw no ...
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 Free
Top 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

Fixed in https://github.com/petyosi/react-virtuoso/commit/16aca7514beefdc9a54e9f920337b46759acd45d.
Ya, I think the bug is fixed in 2.2.6. Just tried it in sandbox for a solid 2 minutes (Windows 10, Microsoft Edge), don’t see this happening again.
I think you can reference the commit and close this issue.
Thks for your effort!