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

Strict mode compatibility #1353

Open
NeoLegends opened this issue Mar 28, 2019 · 19 comments
Open

Strict mode compatibility #1353

NeoLegends opened this issue Mar 28, 2019 · 19 comments
Labels
Milestone

Comments

@NeoLegends
Copy link

RV makes use of findDOMNode in WindowScroller and that's deprecated in recent versions of react. You might want to switch this to using refs instead. :)

@Ericnr
Copy link

Ericnr commented Aug 10, 2019

@bvaughn can this be addressed? Concurrent mode is coming and it'd be nice if the library worked smoothly with it.

@jktravis
Copy link

It also seems to be used in CellMeasurer

@Hypnosphi
Copy link
Contributor

Hypnosphi commented Dec 30, 2019

In WindowScroller, it can be avoided by using registerChild render prop

I'm going to open a PR adding the same pattern for CellMeasurer

UPD: #1477

@Hypnosphi
Copy link
Contributor

Hypnosphi commented Jan 10, 2020

Even if I use registerChild, WindowScroller doesn't seem to work with StrictMode:

https://codesandbox.io/s/react-virtualized-list-with-width-100-dunc2

You can see that if you scroll list down, new items don't appear. This can mean that there are side effects in places where they shouldn't be

https://reactjs.org/docs/strict-mode.html#detecting-unexpected-side-effects

@wuweiweiwu wuweiweiwu added the bug label Jan 10, 2020
@wuweiweiwu wuweiweiwu added this to the 10.0.0 milestone Jan 10, 2020
@wuweiweiwu
Copy link
Collaborator

Thanks for bringing this up! I kinda lost track of some bugs. Will prioritize!

@makker
Copy link

makker commented Jan 14, 2020

Would be awesome to get the strict mode issue fixed. Thanks for the great work so far!

@HeikkiMoilanen1
Copy link

Hello! Are there any news on this one? Would be awesome to get rid of those warnings cluttering the console :). Thank you for the effort and the nice library!

@mika-kaki
Copy link

I'd appreciate a fix for this. Thanks for great work!

@Kudo
Copy link

Kudo commented Sep 3, 2020

This codesandbox example seems to be fixed after upgrading to RV 9.22, maybe it is related to #1477

@kierancrowntrt
Copy link

This codesandbox example seems to be fixed after upgrading to RV 9.22, maybe it is related to #1477

This codesandbox isn't working as of 30/09/20. New items are not being rendered

@timminata
Copy link

Also keen to see a fix for this. We use react-virtualized and are considering trialing React concurrent and I'm not sure if this will just be an annoyance or cause actual errors.

@sergeyzwezdin
Copy link

Not sure, why need findDOMNode() here if we already have ref there?

const Grid = findDOMNode(this.Grid);

@reliveyy
Copy link

Not sure, why need findDOMNode() here if we already have ref there?

const Grid = findDOMNode(this.Grid);

A simple workaround would be const Grid = this.Grid._scrollingContainer;

@meotimdihia
Copy link

@bvaughn please take a look at this problem. It is annoying and takes up space when seeing it at the browser's console.
And we can't suppress this warning too.

SPodjasek added a commit to inway/react-virtualized that referenced this issue Oct 12, 2022
@mleister97
Copy link

Is this lib still maintained? Issue exists still beginning of 2019...

@sebkasanzew
Copy link

Maybe this is a good alternative to this package. But I didn't have the time to try it yet.
https://github.com/tanstack/virtual

@michaelyohanes
Copy link

still occuring on 2024

@githubdev99
Copy link

Also this issue affects my website (which uses Next.js).
image

@meotimdihia
Copy link

we had https://github.com/inokawa/virtua ( a new and better package )

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests