W3C home > Mailing lists > Public > public-html@w3.org > February 2013

[Bug12409] inputmode="latin-prose" sufficient for autocapitalize use cases?

From: Travis Leithead <travis.leithead@microsoft.com>
Date: Sat, 2 Feb 2013 00:14:26 +0000
To: "pecoraro@apple.com" <pecoraro@apple.com>, "mounir@lamouri.fr" <mounir@lamouri.fr>, "kennyluck@csail.mit.edu" <kennyluck@csail.mit.edu>, "cmhjones@gmail.com" <cmhjones@gmail.com>, "public-html@w3.org" <public-html@w3.org>
Message-ID: <9768D477C67135458BF978A45BCF9B3853BC775A@TK5EX14MBXW602.wingroup.windeploy.ntdev.microsoft.com>
Bug 12409 [1] proposes a new input element attribute "autocapitalize" with the following enumerated values:
* none - no capitalization should be performed by a soft keyboard
* sentences - suggest that sentences start with a capital
* words - suggest that each word is capitialized
* characters" - suggest that caps-lock be enabled.

In bug 12885, the "inputmode" attribute was added with support that overlaps this proposal. It seems that:
* inputmode="latin-name" maps to the "words" proposal above
* inputmode="latin-prose" maps to the "sentences" proposal above.

However, the inputmode attribute does not seem to capture the "characters" scenario: input for a form field expecting US-state codes (e.g., WA, TX, NY).

Ted, do you think the inputmode attribute sufficiently addresses your use cases? Do you think we should consider the "characters" scenario for addition to inputmode? (e.g., "latin-yelling")

If you're happy with inputmode as-is we can resolve won't fix. 


[1] https://www.w3.org/Bugs/Public/show_bug.cgi?id=12409
Received on Saturday, 2 February 2013 00:15:18 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 10:16:31 UTC