CfC: publish new WD of IME API; deadline August 12

Below, Takayoshi proposes WebApps publish a new WD of IME API and this 
is a Call for Consensus to do so using the following ED as the basis for 
the WD:

<https://dvcs.w3.org/hg/ime-api/raw-file/default/Overview.html>

Agreement to this proposal: a) indicates support for publishing a new 
WD; and b) does not necessarily indicate support of the _contents_ of 
the WD.

If you have any comments or concerns about this proposal, please reply 
to this e-mail by August 12 at the latest. Positive response to this CfC 
is preferred and encouraged and silence will be assumed to mean 
agreement with the proposal.

Takayoshi - assuming this CfC passes, when you prepare the WD version, I 
think it would be useful if you added your `changes since last 
publication` data as a non-normative appendix. (F.ex. as Joshua did 
recently for the IDB CR 
<http://www.w3.org/TR/2013/CR-IndexedDB-20130704/#revision-history>.)

-Thanks, AB


-------- Original Message --------
Subject:  Update of the IME API spec
Resent-Date:  Fri, 2 Aug 2013 08:42:08 +0000
Resent-From:  <public-webapps@w3.org>
Date:  Fri, 2 Aug 2013 17:41:17 +0900
From:  ext Takayoshi Kochi (河内 隆仁) <kochi@google.com>
To:  public-webapps <public-webapps@w3.org>



Hi all,

It's been a while since the last update for the IME API spec in April.
I would like to push this version to publish a new working draft.

Here's the current cut of editor's draft:
https://dvcs.w3.org/hg/ime-api/raw-file/default/Overview.html
(and log https://dvcs.w3.org/hg/ime-api/log)

Any comments are welcome.

Here are highlights of the changes since the last working draft (20130404):

* Example/use cases/best practices
- Removed Javascript IME use-case
- Removed example1 (drawing composition text in <canvas>)
- Added example code for drawing composition text.
- Added an explanation of InputMethodContext's scope in best practices 
section.

* API
- Added target attribute proposed by Microsoft [1]
- Renamed getInputContext() to .inputMethodContext per comment from James Su
[2]
- Marked composition and target attributes as nullable.
- Clarified that context is associated with one editable or focusable 
element.
- Clarified the scope of setCaretRectangle()'s coordinates.
- Removed confusing 'enabled' property and open() method in favor of
usual focus control and inputmode attribute.
- Changed composition interface. the 'text' property was changed to plain
DOMString from Node, the 'caret' property was divided into the
'selectionStart' and the 'selectionEnd' properties. Added the 'segments'
property to represent the position of segmentation of composition text.

[1] Microsoft proposal:
https://dvcs.w3.org/hg/ime-api/raw-file/tip/proposals/IMEProposal.html
[2] Comment from James Su
http://lists.w3.org/Archives/Public/public-webapps/2013AprJun/0361.html

Thanks in advance,
-- 
Takayoshi Kochi

Received on Monday, 5 August 2013 15:52:48 UTC