Search Results
| Search type | Search syntax |
|---|---|
| Tags | [tag] |
| Exact | "words here" |
| Author |
user:1234 user:me (yours) |
| Score |
score:3 (3+) score:0 (none) |
| Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
| Views | views:250 |
| Code | code:"if (foo != bar)" |
| Sections |
title:apples body:"apples oranges" |
| URL | url:"*.example.com" |
| Saves | in:saves |
| Status |
closed:yes duplicate:no migrated:no wiki:no |
| Types |
is:question is:answer |
| Exclude |
-[tag] -apples |
| For more details on advanced search visit our help page | |
Results tagged with keypad
Search options not deleted
user 113577
1
vote
1
answer
1k
views
Use native keypad or custom one in web application
I'm stuck on how to implement this, basically I came up with these two scenarios:
Use the native built-in keypad
(+) Built-in, accessibility
(-) Requires an initial tap to trigger the keypad
(-) Requires … Use a custom HTML/JS keyboard, basically a grid of buttons
(-) Accessibility
(-) Keypad needs to fit on screen on every device
(+) No initial tap required to trigger a keypad
(+) Consistent look and …
- 111