Re: Only Text Input and Intention Events: Return key

12.12.2014, 12:12, "Norbert Lindenberg" <w3@lindenbergsoftware.com>:
>>  On Dec 5, 2014, at 8:21 , Koji Ishii <kojiishi@gmail.com> wrote:
>>  There are two ways to handle IME inputs for text inputs. I don't know
>>  if there were common terminologies, but a complex one requires several
>>  interactions between IME and text input controls, and therefore editor
>>  framework needs to be aware of that.
>>
>>  While most browsers today implement the complex one, I'd be fine to
>>  defer that to level 2 of the spec or later.
>>
>>  If we can agree on that, the simple one is no different from 'insert
>>  text' as Ben said.
>
> Wouldn’t the “complex” input methods include pretty much all Chinese, Japanese, and Korean input methods on desktop computers?

And maybe not only desktop.

The way I envision this is that the browser handles the input first, so if it is inserting text through some complex IME (in Yandex we allow the user to e.g. type part of a word, then we can offer auto-complete suggesting both latin-based and cyrillic-based words. In the simple case, and this actually includes del/backspace/newline characters (although they may only sometimes be what "enter" means), you insert a run of text - 1 or more characters...

But if that introduces a problem (e.g. you wanted to paste across an element boundary, or add a new element) the browser passes the insertText event with the text generated, as data…

del/backspace/enter are likely to generate requests beyond insertText at least some of the time. insertText on its own might do that, e.g. when it tries to happen in a selection spanning elements, but when it is straightforward, can we not just leave it to happen?

(This is a real question - I don't know the answer, which depends on what everyone is prepared to do…)

cheers

Chaals

--
Charles McCathie Nevile - web standards - CTO Office, Yandex
chaals@yandex-team.ru - - - Find more at http://yandex.com

Received on Friday, 12 December 2014 09:25:37 UTC