Re: inputmode attribute

Travis, thanks for the background.

I'll survey other platforms for other possible (or impossible) values.


On Wed, Jun 5, 2013 at 4:52 AM, Travis Leithead <
travis.leithead@microsoft.com> wrote:

>  Even though our proposal has the combined list, we don’t have a strong
> opinion about whether this should all be in one attribute or in two.
> Primarily, our concern was to add the values are that currently not present
> in the spec, such as full/half width, hiragana/katakana, etc.****
>
> ** **
>
> ** **
>
> *From:* Takayoshi Kochi (河内 隆仁) [mailto:kochi@google.com]
> *Sent:* Monday, June 3, 2013 2:26 AM
> *To:* public-webapps
> *Subject:* inputmode attribute****
>
> ** **
>
> Hi all,****
>
> ** **
>
> For IME API (http://www.w3.org/TR/ime-api/), we got comment from
> Microsoft to change some of types****
>
> from inputmode, which is currently defined as****
>
>
> http://www.whatwg.org/specs/web-apps/current-work/multipage/association-of-controls-and-forms.html#input-modalities:-the-inputmode-attribute
> ****
>
> ** **
>
> and the new proposal is****
>
>
> https://dvcs.w3.org/hg/ime-api/raw-file/tip/proposals/IMEProposal.html#inputmode-attribute
> ****
>
> ** **
>
> As Mounir already discussed in WHAT WG list back in February,****
>
>
> http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2013-February/038914.html
> ****
>
> there was a discussion to separating mode and script for the attribute.***
> *
>
> ** **
>
> Can we discuss what the attribute should be here in this list?****
>
> ** **
>
> --
> Takayoshi Kochi ****
>



-- 
Takayoshi Kochi