Re: [whatwg] inputmode feedback

2014-02-03 Thread Michael[tm] Smith
Ian Hickson i...@hixie.ch, 2014-01-22 00:54 +: The idea of the inputmode= attribute is that it gives the mode that is most likely to be needed by the user when providing input. There's various modes that seem to make sense: - inserting raw latin-script characters, like passwords,

Re: [whatwg] inputmode feedback

2014-02-03 Thread Ian Hickson
On Mon, 3 Feb 2014, Michael[tm] Smith wrote: Ian Hickson i...@hixie.ch, 2014-01-22 00:54 +: The idea of the inputmode= attribute is that it gives the mode that is most likely to be needed by the user when providing input. There's various modes that seem to make sense: -

Re: [whatwg] inputmode feedback

2014-01-27 Thread Ian Hickson
On Mon, 27 Jan 2014, Takayoshi Kochi (河内 隆仁) wrote: On Wed, Jan 22, 2014 at 9:54 AM, Ian Hickson i...@hixie.ch wrote: Japanese IME (e.g. Microsoft IME) has several modes for typing characters, divided by the category of the set of characters (kana, half-width-kana, alphanumeric,

Re: [whatwg] inputmode feedback

2014-01-26 Thread 河内 隆仁
Hi Ian, On Wed, Jan 22, 2014 at 9:54 AM, Ian Hickson i...@hixie.ch wrote: On Fri, 6 Dec 2013, Yoichi Osato wrote: Our Google Japan members working around IME discussed about inputmode. Proposal: Remove kana, katakana and full-width-latin from inputmode attribute. Because above

Re: [whatwg] inputmode feedback

2014-01-21 Thread Ian Hickson
On Fri, 6 Dec 2013, Yoichi Osato wrote: Our Google Japan members working around IME discussed about inputmode. Proposal: Remove kana, katakana and full-width-latin from inputmode attribute. Because above attributes and others are independent as others say. I don't really understand. What

Re: [whatwg] inputmode feedback

2013-12-16 Thread Michael[tm] Smith
[trimming the Cc list, assuming everybody's subscribed to whatwg@lists.whatwg.org] Takayoshi Kochi (河内 隆仁) ko...@google.com, 2013-12-09 16:18 +0900: ... The point that Yoichi wanted to make was to extract IME-related part of 'intputmode' spec and move out of inputmode, or at least separate

Re: [whatwg] inputmode feedback

2013-12-08 Thread 河内 隆仁
Probably the reason some Japanese banks still use half-width kana is what Ryosuke said, but as Mike saw in Mizuho and Mitsui Sumitomo, they are moving away from forcing user to type in half-width kana directly, they convert on server side - I think this is a good trend. Aside from banking, I

Re: [whatwg] inputmode feedback

2013-12-06 Thread Michael[tm] Smith
Yoichi Osato yoic...@google.com, 2013-12-06 15:46 +0900: Our Google Japan members working around IME discussed about inputmode. Proposal: Remove kana, katakana and full-width-latin from inputmode attribute. Because above attributes and others are independent as others say. For web

Re: [whatwg] inputmode feedback

2013-12-06 Thread 河内 隆仁
Just for a data point, lots of Japanese banks still make user type in half-width katakana. Here are some random examples: http://www.tominbank.co.jp/for_kojin/mobile/topics_hankaku-kana.html 「受取人名(半角カナ)」は、半角30字以内で入力してください。 http://www.shinkin.co.jp/okayama/ibandhib/bizib/02_faq/faq_07.html

Re: [whatwg] inputmode feedback

2013-12-06 Thread Michael[tm] Smith
[Maybe we should take this discussion off-list or talk about it some time soon over lunch or something. For now though, here are some comments.] Takayoshi Kochi (河内 隆仁) ko...@google.com, 2013-12-06 19:53 +0900: Just for a data point, lots of Japanese banks still make user type in half-width

Re: [whatwg] inputmode feedback

2013-12-06 Thread Ryosuke Niwa
On Dec 6, 2013, at 5:30 AM, Michael[tm] Smith m...@w3.org wrote: [Maybe we should take this discussion off-list or talk about it some time soon over lunch or something. For now though, here are some comments.] Takayoshi Kochi (河内 隆仁) ko...@google.com, 2013-12-06 19:53 +0900: Just for a

Re: [whatwg] inputmode feedback

2013-12-05 Thread Yoichi Osato
Our Google Japan members working around IME discussed about inputmode. Proposal: Remove kana, katakana and full-width-latin from inputmode attribute. Because above attributes and others are independent as others say. For web developers that want to manage IME state like native applications, the

Re: [whatwg] inputmode feedback

2013-09-16 Thread Ian Hickson
On Tue, 13 Aug 2013, Yoichi Osato wrote: I have questions about some inputmode attributes. In the desktop case, full-width-latin, kana and katakana look to intend user local IME. Right? I'm not sure what this means exactly. I think whether IME is on or off is very important to user because

Re: [whatwg] inputmode feedback

2013-09-03 Thread Ian Hickson
On Thu, 6 Jun 2013, Jonas Sicking 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

Re: [whatwg] inputmode feedback

2013-08-13 Thread Yoichi Osato
I have questions about some inputmode attributes. In the desktop case, full-width-latin, kana and katakana look to intend user local IME. Right? I think whether IME is on or off is very important to user because some IME have state and show some window to input character. It is much different from

Re: [whatwg] inputmode feedback

2013-08-13 Thread Ryosuke Niwa
On Aug 12, 2013, at 11:28 PM, Yoichi Osato yoic...@google.com wrote: I have questions about some inputmode attributes. In the desktop case, full-width-latin, kana and katakana look to intend user local IME. Right? I think whether IME is on or off is very important to user because some IME

Re: [whatwg] inputmode feedback

2013-08-12 Thread 河内 隆仁
+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

Re: [whatwg] inputmode feedback

2013-06-06 Thread Ian Hickson
On Wed, 13 Feb 2013, Mounir Lamouri wrote: To begin with, I think we should get rid of the latin prefix. The three modes with that prefix are latin, latin-name and latin-prose (Also full-width-latin.) but in none of those situations latin is mandatory. While I think it's appealing, from an

Re: [whatwg] inputmode feedback

2013-03-01 Thread Mounir Lamouri
On 15/02/13 08:28, Takayoshi Kochi (河内 隆仁) wrote: As you probably know, there is also 'ime-mode' CSS style which IE/FF implements (and still proposed in CSS3 UI at http://www.w3.org/TR/css3-ui/#ime-mode), which makes this more complex to use. Is that implemented by some vendors? People may

Re: [whatwg] inputmode feedback

2013-02-22 Thread Ian Hickson
On Wed, 20 Feb 2013, Ryosuke Niwa wrote: Why is name not an input type? There's a section that discusses it a bit: http://whatwg.org/html#the-difference-between-the-field-type,-the-autofill-field-name,-and-the-input-modality -- Ian Hickson U+1047E

Re: [whatwg] inputmode feedback

2013-02-20 Thread Ryosuke Niwa
On Wed, Feb 13, 2013 at 11:29 AM, Mounir Lamouri mou...@lamouri.fr wrote: To conclude, Mozilla is interested in implementing this set of keywords: verbatim, text, name, prose and digit (or numeric). Why is name not an input type? How does one decide whether a given semantics should be

Re: [whatwg] inputmode feedback

2013-02-15 Thread 河内 隆仁
Hello Mounir, On Thu, Feb 14, 2013 at 4:29 AM, Mounir Lamouri mou...@lamouri.fr wrote: Regarding the three Japanese specific types, it is not clear if inputmode is the best way to solve the use cases intended to be solved. Actually, 'kana' and 'katakana' are trying to give a hint about the

Re: [whatwg] inputmode feedback

2013-02-15 Thread Jonas Sicking
On Wed, Feb 13, 2013 at 11:29 AM, Mounir Lamouri mou...@lamouri.fr wrote: Hi, Mozilla did implement an inputmode attribute for the input element a few months ago and the HTML specification has been updated after that to introduce that attribute. Given that the specification and our

[whatwg] inputmode feedback

2013-02-13 Thread Mounir Lamouri
Hi, Mozilla did implement an inputmode attribute for the input element a few months ago and the HTML specification has been updated after that to introduce that attribute. Given that the specification and our implementation was not matching, we decided to delay the release of that feature [1] and