WebAPI/KeboardIME: Difference between revisions

WebAPI/KeboardIME (view source)

Revision as of 10:38, 26 July 2013

128 bytes removed , 26 July 2013

→‎Layout Matching Algorithm

Evelyn Hung

Confirmed users

45

edits

@@ Line 89: / Line 89: @@
 When an input field is focused, if its <code>type</code> attribute is one of the allowed values stated above, it will be used to filter a set of candidate layouts. A candidate layout means it can handle this input type or is possible to let user input all characters that this input field can accept.
-For example, if the type of a input is "url", then a layout with "url" or "text" listed in the <code>types</code> of its manifest will be matched. However, if a input field with type "text", then all layouts that support "text" will be matched, but those layouts that only support "url" will not. This is because we believe layouts that can handle "text" could be a fallback for "url" input type, but not vice versa. An input type fallback plan is pre-defined as follows:
+For example, if the type of a input is "url", then a layout with "url" or "text" listed in the <code>types</code> of its manifest will be matched. However, if a input field with type "text", then all layouts that support "text" will be matched, but those layouts that only support "url" will not. This is because we believe layouts that can handle "text" could be a fallback for "url" input type, but not vice versa. We also believe "text" could be a fallback for all allowed types stated above.
-* "text" is the fallback of "textarea", "url", "email", "password", "search", and "contenteditable".
-* "number" is the fallback of "number" and "tel".
 The matching algorithm of keyboard manager in System app is as follows: