You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Are there any examples of how (or indeed, where) Apple support this on iOS? As far as I know there's no built-in way to support navigating content with just a keyboard without some extra work from the developers, so wondering how this is a requirement that Apple handle, or how we're expected to handle it natively.
But as far as I can see it's not natively support out-the-box with a couple of lines of code like most other examples we've got so far.
Note also that gist is just for a UITableView, this doesn't cover UICollectionView or any other type of view that is on screen, so extra work would be needed to support those, as well as support traversing from a table to another element, like a tab bar.
I feel like this is a problem that hasn't yet been solved because it's not part of iOS?
The text was updated successfully, but these errors were encountered:
I've always wondered that. I don't know much about it. It's be great to find out / ask specialists.
So, what happens if I connect a keyboard to my iPhone: can I now use the tab key and the enter key to navigate through content and use functionalities?
Are there any examples of how (or indeed, where) Apple support this on iOS? As far as I know there's no built-in way to support navigating content with just a keyboard without some extra work from the developers, so wondering how this is a requirement that Apple handle, or how we're expected to handle it natively.
There are ways to do it by writing lots of custom code similar to this: https://gist.github.com/adamyanalunas/b1ce3af40843a356dc3cade6e6ab6a21
But as far as I can see it's not natively support out-the-box with a couple of lines of code like most other examples we've got so far.
Note also that gist is just for a UITableView, this doesn't cover UICollectionView or any other type of view that is on screen, so extra work would be needed to support those, as well as support traversing from a table to another element, like a tab bar.
I feel like this is a problem that hasn't yet been solved because it's not part of iOS?
The text was updated successfully, but these errors were encountered: