Maciej, you should know that, currently, if this proposal goes forward the
members of the canvas accessibility subteam believe that this proposal
should be in addition and not a replacement for the existing proposal.
Rich
Rich Schwerdtfeger
CTO Accessibility Software Group
From: Maciej Stachowiak <mjs@apple.com>
To: Charles McCathieNevile <chaals@opera.com>
Cc: Sam Ruby <rubys@intertwingly.net>, Ian Hickson <ian@hixie.ch>,
HTML WG <public-html@w3.org>
Date: 06/24/2010 12:06 AM
Subject: Re: CfC: Adopt ISSUE-105 canvas-usemap Change Proposal to add
usemap attribute to the canvas element
Sent by: public-html-request@w3.org
On Jun 23, 2010, at 4:46 PM, Charles McCathieNevile wrote:
Since you think the proposal was a bad idea, there must be a counter
proposal you can write that isn't a bad idea. Given that the proposal
is "Add an attribute", (and assuming that it copies the sentence or
so to give you complete explicit editing instructions to execute the
proposal), I would expect a counter proposal that explains *why* it
is a bad idea to document the existing behaviour of browsers in this
way.
Are you saying that browsers actually do something when a usemap attribute
is present on the canvas element? Which browsers? Do you have a test case?
Regards,
Maciej
