- From: <bugzilla@jessica.w3.org>
- Date: Sat, 02 Feb 2013 00:14:14 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=12409
Travis Leithead [MSFT] <travil@microsoft.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |travil@microsoft.com
Assignee|eoconnor@apple.com |travil@microsoft.com
--- Comment #13 from Travis Leithead [MSFT] <travil@microsoft.com> ---
This 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.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Saturday, 2 February 2013 00:14:16 UTC