Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[BUG] Scroll & rerenders during layout animations mess up position
See original GitHub issue- text-declared colors, like
redstoped animating (with console warning), but maybe that is intentional. If not - can open separate issue.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:2
- Comments:11
Top Results From Across the Web
Having a rendering issue with React-Native Animation
1 Answer 1 · The main problem is because you don't store the state of each card properly (if it is flipped or...
Read more >Layout animations | Framer for Developers
Layout animations. Create layout and shared layout animations with React and Framer Motion. CSS layouts are difficult and expensive to animate.
Read more >overscroll-behavior - CSS: Cascading Style Sheets | MDN
The overscroll-behavior CSS property sets what a browser does when reaching the boundary of a scrolling area.
Read more >Common bugs in React Native ScrollView and how to fix them
React Native's ScrollView component is ubiquitous, but its implementation can sometimes lead to mistakes. Learn what to look out for here.
Read more >SectionList - React Native
Section header support. Section separator support. Heterogeneous data and item rendering support. Pull to Refresh. Scroll loading.
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
That’s actually quite informative still thanks for the extra info
Is this issue related to https://github.com/framer/motion/issues/940 (and specifically, https://github.com/framer/motion/issues/940#issuecomment-847427853)?