+Yoichi Osato, who is working on implementing inputmode spec for Blink and Chromium.
On Fri, Jun 7, 2013 at 8:04 AM, Jonas Sicking <jo...@sicking.cc> wrote: > On Thu, Jun 6, 2013 at 2:08 PM, Ian Hickson <i...@hixie.ch> wrote: > > On Fri, 15 Feb 2013, Jonas Sicking wrote: > >> > >> Using semantic names might give us the warm fuzzies, but is there really > >> any semantic use we will get out of these that we wouldn't by using > >> "lowercase", "titlecase" or "autocapitalized"? > > > > The reason I used the more "semantic" names is that the names like > > "lowercase", "titlecase" or "autocapitalized" aren't accurate. For > > example, you can hit shift in "lowercase" mode to get uppercase. You can > > have a "titlecase" mode that doesn't capitalise every word (e.g. it > > recognises the "van" in "van Kesteren"). A value that is explicitly for > > names can use a different dictionary than one that is just for > capitalised > > text (e.g. derived from the user's contact list). And so on. > > > > > >> I take it verbatim and name would disable any spelling corrections, > >> and name would also titlecase? But the difference between text and > >> prose seems really hard to understand. > > > > In the spec, "verbatim" does not correction at all, e.g. passwords; > > "latin" is for human-to-computer communications, e.g. free-form text > > search fields, and would do spelling correction and automatically > > inserting spaces between words in swiping keyboards, etc; and > > "latin-prose" is intended for human-to-human communications, with > > aggressive automatic typing correction, e.g. text prediction and > automatic > > capitalisation at the start of sentences. > > I think a really important question is if this is understandable to > authors. There's also a big risk that if these modes aren't noticeably > different in initial implementations, it will be hard to add such > differences later. > > / Jonas > -- Takayoshi Kochi