W3C home > Mailing lists > Public > whatwg@whatwg.org > November 2010

[whatwg] Proposal: Input Method Editor API

From: Ryosuke Niwa <rniwa@webkit.org>
Date: Wed, 10 Nov 2010 18:17:16 -0800
Message-ID: <AANLkTikpKP0RT4ZeZNbs3xnraYHCOQUKfB5=9EcCLrq3@mail.gmail.com>
Hi,

There's a typo in CompositionClause section.  Namely, the interface is
labelled CompositionAttribute as supposed to CompositionClause.

We should have isEnabled and getCaretRectangle for InputMethodContext.  This
section should also be moved before Composition Interface since (I assume)
getInputContext() returns InputMethodContext.  You should probably say what
happens when an invalid (or inconsistent) composition object is passed to
setComposition as well.

Does confirmComposition finish the composition and forces UA to "type" the
current composition?  i.e. will the current composition be inserted as typed
text?  I just don't understand how this function will interact with other
DOM events, APIs, etc.. Could you clarify?

In InputMethodManager section, you should mention that this is added to the
window object. I'm not sure if passing x, y, w, h for setCaretRectangle is
really useful.  Wouldn't it be better for setCaretRectangle to take a DOM
node?  I would think that the composition text is inside some HTML element
in typical cases and I feel it's an added work for the script to figure out
what x, y, w, and h of the node are.  Also, what happens the composition
text spans more than one visible line?  As far as I know, the candidate
window is always at the end of the composition text.  However, if we have a
composition text that spans more than one visible line, then the area
occupied by the composition text won't be a rectangle.  What should the web
page supply as the rectangle in this case?

Best regards,
Ryosuke Niwa
Software Engineer
Google Inc.

2010/11/9 Hironori Bono (?? ??) <hbono at google.com>

> Greetings,
>
> I'm Hironori Bono, a software engineer of Google. In the
> w3c-international ML, we have been discussing to write a proposal that
> adds an IME API to HTML5. This proposal is not only for web
> applications to control a system IME but also to write an IME in
> JavaScript. Even though this proposal is still an infant phase, I
> would like to post it to whatwg to hear comments from HTML experts.
> Would it be possible to read the following document and give me your
> comments?
>
>
> https://docs.google.com/fileview?id=0B8eVDHQ9_22-MzJhMTg2YmItNWU3NC00NzJmLThlMTAtYmU1ZTBlZWJhNzM0&hl=en&authkey=CLLHkFw
>
> Thank you for your interest in advance.
>
> Regards,
>
> Hironori Bono
> E-mail: hbono at google.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20101110/588726f2/attachment.htm>
Received on Wednesday, 10 November 2010 18:17:16 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:28 UTC