- From: <bugzilla@jessica.w3.org>
- Date: Mon, 16 Dec 2013 09:23:04 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23961 --- Comment #4 from Michael[tm] Smith <mike@w3.org> --- (In reply to Ben Bucksch from comment #1) > I propose to split up the different aspects: > > For 1. above: > * inputscript="latin"/"kana" etc. > default is chosen by browser based on language of page and user. > See > http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org//2013-February/038914. > html > > For 2. above: > * type="email"/"url"/"text" > As already specced > > For 3. above: > * autocorrect="off" (change words that the user already typed) > * autocapitalization="off" > * spellcheck="off" (underline misspelled, with aids to correct on user > action) > * typingaids="off" (Swipe, word suggest; not changing letters the user typed) > I'm not sure about this last one. Before adding any more new attributes, I think it'd be a good idea to see if the stakeholders (especially the implementors) are interested in extending the syntax of the existing inputmode attribute to allow for things like what you have in your category 3. That's actually the way that the inputmode attribute was originally specified, when it first appeared in the XForms spec, and then in the XHTML Basic spec, and then in Web Forms 2.0. The original idea was that the attribute value could contain a list of tokens: an optional script token and one more modifier tokens: http://www.w3.org/TR/2003/PR-xforms-20030801/sliceE.html#mode-modifiers So you could have value like inputmode="latin titlecase typingaids". -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Monday, 16 December 2013 09:23:10 UTC