2.6.6 release not compatible with `unmountIfInvisible` prop
See original GitHub issueWe are using react-lazyload
to only mount a resource-heavy component only when it’s visible. The unmountIfInvisible
option is ideal for that and previously worked perfectly.
As of the latest release this has broken. It will now intermittently mount and unmount while scrolling.
While I’m not overly familiar with your codebase, it seems the ref will always point to the one for the placeholder. In 2.6.5, this would refer to either the placeholder or the loaded component depending on which is visible. I think it might be causing it to unmount early as the visibility check then returns false
.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:10 (1 by maintainers)
Top Results From Across the Web
Spring Boot 2.6.6 available now
6 has been released and is now available from Maven Central. The Spring Framework version in this release includes a fix for CVE-2022-22965, ......
Read more >react-lazyload - npm
Lazyload your components, images or anything where performance matters.. Latest version: 3.2.0, last published: 2 years ago.
Read more >Spring boot 2.6.7 incompatibility with spring-cloud-context 3.1 ...
7] is not compatible with this Spring Cloud release train Action: Consider applying the following actions: - Change Spring Boot version to one ......
Read more >Migrate spring boot app from 2.4.4 to 2.6.6 we are getting ...
We migrate our application spring boot-2.4.4 to 2.6.6 and below Denodo ... candidates were found but could not be injected: - User-defined ...
Read more >The Spring Boot Starter Parent | Baeldung
We just need to re-declare the property with a new value. For example, to change the Java version, we can indicate it in...
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
@ameerthehacker Because the impact is relatively large, I rolled back the code to 2.6.7
@ameerthehacker I’ve tried out the beta version and everything’s working great.
Thanks for sorting it out so quickly. Much appreciated!