- From: 坊野 博典 <hbono@google.com>
- Date: Fri, 22 Jun 2012 11:21:00 +0900
- To: Dominique Hazael-Massieux <dom@w3.org>
- Cc: public-webapps@w3.org
Greetings Dom, This is just for your information. I have pushed a change that applies your comments: <http://dvcs.w3.org/hg/ime-api/rev/420725ab06cd>. Regards, Hironori Bono E-mail: hbono@google.com On Tue, Jun 5, 2012 at 6:16 PM, Hironori Bono (坊野 博典) <hbono@google.com> wrote: > Greetings Dom, > > Thanks for your bug reports and sorry for my slow response. > I will update this draft next week to apply them. (Unfortunately, I > cannot afford to fix this draft this week.) > > Regards, > > Hironori Bono > E-mail: hbono@google.com > > On Mon, Jun 4, 2012 at 4:19 PM, Dominique Hazael-Massieux <dom@w3.org> wrote: >> Hi, >> >> I spotted a few bugs in the WebIDL fragments of the Input Method Editor >> API draft [1]that I'm reporting below. I'm happy to bring the required >> changes directly to the draft if that's preferred. >> >> -------------- >> interface HTMLElement >> … >> Object getInputContext (); >> }; >> >> should be >> >> partial interface HTMLElement >> InputMethodContext getInputContext (); >> }; >> (assuming this interface is really to be added to HTMLElement) >> >> -------------- >> CompositionClauseList is a typedef of a sequence type but is used for an >> attribute; sequences are not appropriate type of attributes, you would >> want to use an array instead. >> >> -------------- >> "int" is not a valid WebIDL type, you would want to use either "short", >> "long" or "long long" >> >> -------------- >> Composition, CompositionCaret and CompositionClause should probably be >> dictionaries rather than interfaces. That would also allow to define >> default values directly in the IDL. >> >> -------------- >> The methods in InputMethodContext uses the "in" keyword that is no >> longer a valid WebIDL keyword. >> >> >> Dom >> >> 1. http://www.w3.org/TR/2012/WD-ime-api-20120524/ >> >> >>
Received on Friday, 22 June 2012 02:21:29 UTC