W3C home > Mailing lists > Public > public-html@w3.org > June 2010

Re: CfC: Adopt ISSUE-105 canvas-usemap Change Proposal to add usemap attribute to the canvas element

From: Lachln Hunt <lachlan.hunt@lachy.id.au>
Date: Thu, 24 Jun 2010 12:32:58 +0200
Message-ID: <4C23345A.7010007@lachy.id.au>
To: Charles McCathieNevile <chaals@opera.com>
Cc: HTML WG <public-html@w3.org>
On 2010-06-23 19:00, Charles McCathieNevile wrote:
> On Wed, 23 Jun 2010 01:10:06 -0700, Ian Hickson <ian@hixie.ch> wrote:
>> On Tue, Jun 15, 2010 at 4:05 AM, Sam Ruby <rubys@intertwingly.net> wrote:
>>> http://www.w3.org/html/wg/wiki/ChangeProposals/addimagemaptocanvas
>> Sorry for the delay, I missed this call. I object to this
>> proposal, ... and it has a vastly higher implementation cost than
>> is justified  by the authoring benefit derived.
> What is the implementation cost? We do this in Opera right now. A smoke
> test shows that FF and Safari do as well. Those are the three browsers I
> have to hand, but I would be interested in the evidence that this is an
> implementation cost (rather than having to change existing browser code
> to change the way the Web works today).

You seem to be mistaken.  No browser currently implements usemap on 
canvas.  What test case did you use that led you to believe that it works?

Here's a demo I made to illustrate this.


Lachlan Hunt - Opera Software
Received on Thursday, 24 June 2010 10:33:29 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 9 October 2021 18:45:20 UTC