A user account is required in order to edit this wiki, but we've had to disable public user registrations due to spam.

To request an account, ask an autoconfirmed user on IRC (such as one of these permanent autoconfirmed members).

Difference between revisions of "Text input keyboard mode control"

From WHATWG Wiki
Jump to: navigation, search
(Android Japanese IMEs)
(English: moving Japanese stuff)
Line 36: Line 36:
 
<img src="https://lh6.googleusercontent.com/--tbavGIBX30/UAXmZMrQFTI/AAAAAAAASsY/LPuXhDp-VG0/s512/Screenshot_2012-07-17-15-16-47.png">
 
<img src="https://lh6.googleusercontent.com/--tbavGIBX30/UAXmZMrQFTI/AAAAAAAASsY/LPuXhDp-VG0/s512/Screenshot_2012-07-17-15-16-47.png">
 
<img src="https://lh6.googleusercontent.com/--lhwXP8Qt5s/UAXmXK0oUVI/AAAAAAAASsA/ozve-EtDonE/s512/Screenshot_2012-07-17-15-23-40.png">
 
<img src="https://lh6.googleusercontent.com/--lhwXP8Qt5s/UAXmXK0oUVI/AAAAAAAASsA/ozve-EtDonE/s512/Screenshot_2012-07-17-15-23-40.png">
 
==== Android Japanese IMEs====
 
 
Four basic modes:
 
* kana input [あ]
 
* roman-alphabet input [A]
 
* number input [1]
 
* symbol input [☺ or (^_^)]
 
 
Here are three examples of kana mode, using respectively the ATOK, Google, and Samsung IMEs on Android:
 
 
<img src="http://people.w3.org/mike/mobile-ime/atok.png" alt="ATOK IME" title="ATOK IME">
 
<img src="http://people.w3.org/mike/mobile-ime/google.png" alt="Google IME" title="Google IME">
 
<img src="http://people.w3.org/mike/mobile-ime/samsung.png" alt="Samsung IME" title="Samsung IME">
 
  
 
== Existing APIs ==
 
== Existing APIs ==

Revision as of 08:16, 20 July 2012

See also http://www.w3.org/Bugs/Public/show_bug.cgi?id=12885 and http://www.w3.org/Bugs/Public/show_bug.cgi?id=12409 and yet another CSS proposal — 'input-mode'. Mozilla bug: https://bugzilla.mozilla.org/show_bug.cgi?id=746142

Existing kinds of keyboards

English

iOS

  • Telephone number input
  • Numeric input
  • E-mail address input
  • Text input

(Images hotlinked from this StackOverflow post: http://stackoverflow.com/questions/773843/iphone-uiwebview-how-to-force-a-numeric-keyboard-is-it-possible )

Android

  • Text input with leading capitalisation
  • Username / password input? (no capitalisation)
  • Text input without capitalisation in a search context (search submission button)
  • Numeric input (big 0-9 keys, +, -)
  • Telephone number input (big 0-9 keys, *, #)
  • URL input (keys for /, "www.", ".com")
  • Email input (keys for @, '-', ".com")

Existing APIs

XForms

XForms uses a model of modifiers ("startUpper", "predictOff", "digits", etc) and script block names ("simplifiedHanzi", "tagalog", "canadianAboriginal", etc).

Example: http://www.w3.org/TR/xforms/#mode-examples

Proposed API

Gecko

  • 'numeric': 0-9, +, -, comma, dot;

Use case: to have a vkb similar to <input type='number'> without the UI and other stuff that come with <input type='number'>. That could be used for other stuff than numbers for example.

  • 'digit': 0-9 only;

Use case: to write digits without being numbers like social security number or credit card number.

  • 'uppercase': A-Z only;

Use case: obvious, could even be used on desktop.

  • 'lowercase': a-z only;

Use case: obvious, could even be used on desktop.

  • 'titlecase': uppercase character for each new word;

Use case: obvious, could even be used on desktop.

  • 'autocapitalized': first letter is uppercased;

Use case: obvious, could even be used on desktop. Also, that would be a parity feature for iOS autocapitalized attribute.

Except 'number' it's not obvious that we should have input modes similar to input types (like email, tel, url). Actually, we could even discuss the use case of 'number'.
This is intended to be a small set of quite obvious input modes. Some other might be useful.