Step to tap row in table view attempts to scroll to the row when not visible yet
Build armv6 architecture for iPod
Fix premature timeout in wait for interval step
Step to tap row in table view attempts to scroll to the row when not visible yet
Build armv6 architecture for iPod
Fix premature timeout in wait for interval step
Merge remote-tracking branch 'origin/master'
Add explicit ivar declarations to UITouch headers to ensure compatibility with UITouch.h headers
that no longer declare ivars.
Use availability macro to ensure clean build against 5.0 SDK
Fix warning from unsigned long long format string
Use scrollRectToVisible: instead of setContentOffset: when bringing elements within a scroll view into the
visible field. This prevents jerkiness in the positioning and works around elements scrolled off screen that
fail to be found under iOS 6.
Merge pull request #129 from GateGuru/unsigned-long-long-warning

Fix warning from unsigned long long format string
Merge pull request #128 from GateGuru/127-uitouch-ivars-fix

Fixes breakage due to ivar changes in UITouch.h
Merge pull request #130 from GateGuru/fix-jerky-scrolling

Use scrollRectToVisible: instead of setContentOffset: on UIScrollView
Introduces a new step to wait for the first responder to equal the view or accessibility element with a given accessibility label
Fix ARC breakage due to autorelease invocation in KIFTestWaitCondition
Merge pull request #133 from GateGuru/bugfix/remove-autorelease-for-ARC

Fix ARC breakage due to autorelease invocation in KIFTestWaitCondition
Merge pull request #132 from GateGuru/feature/verify-first-responder

Introduce step to verify the first responder is equal to a view with a given accessibility label
Merge pull request #125 from paulz/master

Fix several issues came up while using KIF
When the accessibility frame is not set, use the view frame

On the iOS Simulator 5.0, there are times when the Accessibility Inspector will
determine the accessibility frame correctly but the accessibilityFrame property
on the element will be {0, 0, 0, 0}. This happens in some cases when the UI is
created programmatically.

As a work-around when running on 5.0 and prior, this change attempts to
duplicate the OS's behavior of guessing the accessibility frame. It assumes
{0, 0, WIDTH, HEIGHT} where WIDTH and HEIGHT are equal to view.frame.width and
view.frame.height.