Implementing a Sticky Input Field in iOS

Post by sandofsky » Sun, Aug 09, 2015, 10:28 PM UTC

ayrkm wrote: post #9

sandofsky wrote: post #8

There's no mention in the article that since iOS 7, there's been a "UIScrollViewKeyboardDismissMode", which allows "interactive" dismissal. It isn't perfect, but the last time I investigated, too many solutions out there involved touching private APIs.

I could've more explicit. Interactive dismissal only made possible with UIScrollViewKeyboardDismissModeInteractive introduced since iOS 7. This article described solution for interactive dismissal with `sticky` input field atop the keyboard.

Post by ayrkm » Mon, Aug 10, 2015, 2:53 AM UTC

sandofsky wrote: post #11

ayrkm wrote: post #9

Earlier quoted context omitted.

I could've more explicit. Interactive dismissal only made possible with UIScrollViewKeyboardDismissModeInteractive introduced since iOS 7. This article described solution for interactive dismissal with `sticky` input field atop the keyboard.

In 2015, most apps shouldn't support anything below iOS 7. Create a constraint that attaches the input field to the bottom of the scrollview. One tradeoff is that dismissal doesn't start until your touch enters the real keyboard area. I'll take it, since it's safer than using KVO to observe private APIs.

Post by ayrkm » Mon, Aug 10, 2015, 3:34 PM UTC

sandofsky wrote: post #14

ayrkm wrote: post #13

Earlier quoted context omitted.

Hi sandofsky, that was our previous implementation (dismissal starts only when user's touch enters the real keyboard area) - it doesn't feel 'right'. The library is not really using KVO to observe private APIs, bounds/center of UIView is public property.

You're observing the superview in a hierarchy you don't own. In your code, you have an iOS version check, presumably since the property you're looking for changed between iOS versions.

Post by ayrkm » Mon, Aug 10, 2015, 4:29 PM UTC

sandofsky wrote: post #16

ayrkm wrote: post #15

Earlier quoted context omitted.

yes, that I agree, it may break between iOS versions. i'm all ear to other approach if any

You file a ticket with Apple and stick with documented APIs.

Post by ayrkm » Mon, Aug 10, 2015, 5:46 PM UTC

sandofsky wrote: post #18

ayrkm wrote: post #17

Earlier quoted context omitted.

will do and hope Apple may do something about that. until then, will stick to current solution and test ahead of any new iOS release.

You've decided on the path of higher maintenance, and you've increased the risk of Apple rejection. Maybe this decision won't bite you, but this mentality will.