- From: Travis Leithead <travis.leithead@microsoft.com>
- Date: Sat, 9 Feb 2013 00:03:25 +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>, "Edward O'Connor (eoconnor@apple.com)" <eoconnor@apple.com>
Ted, any comment as you filed this bug? > From: Travis Leithead > > 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. > > Thanks! > > [1] https://www.w3.org/Bugs/Public/show_bug.cgi?id=12409
Received on Saturday, 9 February 2013 00:04:23 UTC