3 ms·
In case anyone is wondering, this plugin hides the "accessibility bar," i.e. the keyboard bar that appears when you tap on a form element in iOS: https://nolanw
by nolanl 11y ago
In case anyone is wondering, this plugin hides the "accessibility bar," i.e. the keyboard bar that appears when you tap on a form element in iOS: https://nolanwlawson.files.wordpress.com/2016/03/accessibility_bar.png https://nolanwlawson.files.wordpress.com/2016/03/accessibili...
The accessibility bar is really annoying for hybrid app developers, because it's often not needed, and just takes up valuable screen real estate. As one of my coworkers put it, it has no purpose other than to announce, "Hi! I'm a WebView!"
- blkhp19 11y agoWell, that's what happens when you don't write native apps.
- minikites 11y agoI'm having trouble thinking of cases when it isn't needed, do you have a simple example?
- nolanl 11y agoLet's say you have one big contenteditable, so there's only one field, and it's pointless to have "previous," "next", and "done" buttons. Or just any situation where you don't think the user needs to be able to switch left and right and can tap instead. Or situations where you want to make your own UI instead of using the default Safari UI.
- minikites 11y agoBut the "Done" button would hide the keyboard so you can see more of the text to review it, right? It just seems user-hostile to remove system features that otherwise always appear.