On Thu, May 2, 2013 at 9:44 AM, Takayoshi Kochi (河内 隆仁)
wrote:
> Before getting into details, is it appropriate to discuss CSS properties
> (ime-*) and HTML attribute (inputmode) here?
>
> At least, I think I should not incorporate CSS/HTML spec into the IME API
> spec, as they are already in the
idateWindowClientRect together with a group of CSS
> properties to give more flexibility for the UI design.
>
> ** **
>
> We also propose several new APIs in InputMethodContext, CSS properties and
> attributes to provide more information and more control around IME. Please
> refer
the text field, and whether it
> is horizontally shifted to follow the caret position. Therefore we are
> proposing getCandidateWindowClientRect together with a group of CSS
> properties to give more flexibility for the UI design.
>
> ** **
>
> We also propose several new A
oposal for more detail.
-Jianfeng Lin
From: Kenji Baheux [mailto:kenjibah...@google.com]
Sent: Tuesday, April 02, 2013 4:32 PM
To: Travis Leithead
Cc: hb...@google.com; ko...@google.com; public-webapps
Subject: Re: [IME] Preparing some feedback
Thanks Travis.
We are eager to hear your feedbac
Thanks Travis.
We are eager to hear your feedback.
The spec was down scoped to exclude Javascript based IME because we could
not find any compelling use case but we would be happy to reconsider if you
do.
2013/3/30 Travis Leithead
> Thanks for submitting these updates to the Input Method Edito
