-
Notifications
You must be signed in to change notification settings - Fork 237
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
Drag/Swipe over a scroll view - the scroll view ends in invalid state #200
Comments
Is this just in the 6.1 simulator, or in 6.0 too? Cheers, PeteTyped on a little bitty keyboard On Apr 25, 2013, at 2:53 PM, ondrejhanslik [email protected] wrote:
|
Reproduced on 6.1, 6.0, 5.1 ipad simulators. Currently I am using the scroll helper as a workaround but I don't like tampering with the content offset directly because I depend on the dragging delegate methods. |
Would you be able to add a example failing test to the Controls app in the repo which demonstrates this issue so I can reproduce locally and look into a fix? Cheers, PeteTyped on a little bitty keyboard On Apr 26, 2013, at 2:44 AM, ondrejhanslik [email protected] wrote:
|
Just tested.
(it's possible you will have to repeat 4. several times) |
I spent the last couple of days trying to understand this issue and I am sure that:
I was able to reproduce the same error using UI Automation: One interesting fact is that the events generated by When When I tried to change |
Very weird issue happening (iOS 6.1 Simulator). When I drag or swipe using the methods in
UIView+PublicAutomation
over a scroll view (or table view or web view), the scroll view correctly scrolls but never stops scrolling (scroll indicator stays visible and the view won't accept any taps).I have experimented with the code inside
UIAutomationBridge
(number of points, gesture duration) and logged theUIEvent
objects delivered to the app and everything seems to be fine with one exception - the latest events from the drag/swipe haveview
set tonil
.Maybe the problem is inside UI Automation framework.
The text was updated successfully, but these errors were encountered: