W3C home > Mailing lists > Public > www-archive@w3.org > April 2011

Re: Working Group Decision on ISSUE-131 caret-location-api

From: Ian Hickson <ian@hixie.ch>
Date: Sat, 30 Apr 2011 18:29:49 +0000 (UTC)
To: Robert O'Callahan <robert@ocallahan.org>
cc: Richard Schwerdtfeger <schwer@us.ibm.com>, Jonas Sicking <jonas@sicking.cc>, jbrewer@w3.org, www-archive@w3.org
Message-ID: <Pine.LNX.4.64.1104301827180.25791@ps20323.dreamhostps.com>
On Sat, 30 Apr 2011, Robert O'Callahan wrote:
> On Sat, Apr 30, 2011 at 6:15 PM, Robert O'Callahan <robert@ocallahan.org>wrote:
> > 
> > As a Mozilla developer, I would not make caret and selection tracking 
> > for canvas a priority until it's clear that discouraging authors from 
> > implementing text editing in canvas has failed.
> 
> (And even then, we'd have to examine the reasons why authors were 
> insisting on writing text editors in canvas. If it's "because they're 
> boneheads", asking them to use special accessibility APIs is probably 
> pointless.)

It's also pointless if the real reason is "the more appropriate API is 
inadeqate", as was the case with Bespin originally (IIRC, they wanted a 
way to do syntax highlighting, which they viewed as being as hard using 
contenteditable="" as using <canvas>, and which is impossible with 
<textarea>). In such a case it would be better to fix the appropriate API 
rather than canvas as well.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Saturday, 30 April 2011 18:30:13 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 7 November 2012 14:18:35 GMT