Re: CfC: Close ISSUE-131: caret-location-api by Amicable Resolution

On 8/22/2012 6:07 AM, Sam Ruby wrote:
> On 08/02/2012 12:59 PM, Richard Schwerdtfeger wrote:
>> */For these reasons I would ask that the chairs move issue 131 to
>> and save proposal
>> /**/ 
>> for
>> review at that time. This will give more time for canvas,
>> contenteditable, web-based IME support, and cross-cutting accessibility
>> support to develop and mature. If the chairs agree to then I would
>> support the chairs decision for HTML5 as a temporary one requiring
>> greater view in the next version, otherwise I will need to formally
>> object to the chairs decision.
> We previously vacated the original issue 131 decision, reopened the 
> issue, and allowed changes to be made:
> Now Richard is asking that we effectively consider his proposal 
> withdrawn for the HTML5 time frame.  Frank has also agreed to postpone 
> this to
> Given that no active proposals remain, the chairs are now asking if 
> there is consensus to roll back the hit testing proposal and to defer 
> the feature to  If anybody would like to raise an objection 
> during this time, we will require them to accompany their objection 
> with a concrete and complete change proposal.

For those following the caret-location-api thread: there are two 
positive developments in this area.

First, there is a reasonable low level IME API:

Second, the basic "scrollPathIntoView()" method of the Canvas 2D API 
allows UAs to treat the current path as a caret and/or selection area.

The critical issue in implementations, currently, is that Range objects 
do not seem to work within the Canvas sub-tree. This may have already 
been addressed in some implementations.
By using Range and scrollPathIntoView it seems that authors can define 
caret location both semantically and spatially. Further, the IME API 
with appropriate baseline information and focus allows for high quality 
IME construction.

It's been several years since this issue was brought up, and many 
lengthy threads about the validity of use cases.

I'm glad to report that the feature-set has made it into W3C specifications.


Received on Wednesday, 22 August 2012 16:30:31 UTC