Dragging view "jitters" on iOS
See original GitHub issueHas anyone experienced the view “jittering” when you drag it? It happens when using:
<KeyboardAwareScrollView keyboardDismissMode='on-drag' keyboardShouldPersistTaps={true}>
Also, it adds extra space at the top and bottom of the view?
Edit: Setting automaticallyAdjustContentInsets={false}
removes the space at the top, not the bottom however.
Issue Analytics
- State:
- Created 7 years ago
- Comments:15
Top Results From Across the Web
Iphone 13 Pro choppy/jittery scrolling - Apple Community
I've noticed choppy / jittery scrolling on my 13 Pro since I got it two weeks ago. I've jsut updated the ios to...
Read more >UIRefreshcontrol jitters when pulled down and held
So I just came across this same problem, and I came up with a solution. Basically, if you pull your tableView down far...
Read more >6 Methods to Fix iPhone YouTube Video Stuck/Lagging on ...
After updated to iOS 15, when you watch video on YouTube with browser or App, you may get stuck, lagging on it. Here...
Read more >Smooth Scrolling in UITableView and UICollectionView
Table views and collection views are both designed to support displaying sets of data that can be scrolled. However, when displaying a very ......
Read more >Performing iOS Animations On Views With UIKit And UIView
You can start moving a view with your finger, then release it and the view will go back to its original position. Alternatively,...
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
try set
enableResetScrollToCoords
to false,this works for me. Besides, I think it should default to false ifresetScrollToCoords
is undefinedI can confirm the @hitbear518 fix. Works fine for me to.