RE: CP is incoherent, and the decision is a vague change to the CP

The problem we have now is that the chairs have not yet responded to:

http://lists.w3.org/Archives/Public/public-html/2011Apr/0496.html

Until that is done Ian does not know what to do as our change proposal
requires that canDrawCustom be removed. Currently the Canvas 2D API spec.
has a bug whereby it allows the author to draw a custom focus ring without
using the drawFocusRing() function to drive the magnifier.

If the chairs accept the change to remove canDrawCustom then Ian can take
my spec. text change in the Change Proposal. There is nothing vague about
doing a cut and paste of the sections. All changes are delimitted by <ZZZ>
and </ZZZ> as has been requested.

Rich

Rich Schwerdtfeger
CTO Accessibility Software Group



From:	Steve Faulkner <faulkner.steve@gmail.com>
To:	HTMLWG WG <public-html@w3.org>, Richard
            Schwerdtfeger/Austin/IBM@IBMUS
Date:	04/26/2011 03:44 AM
Subject:	RE: CP is incoherent, and the decision is a vague change to the
            CP



Hi Ian,

in reference to the canvas CP/decsion you wrote:

# [01:25] <Hixie> the CP is incoherent, and the decision is a vague change
to the CP
# [01:25] <Hixie> there's just no way i want to play this game

I would suggest the best way to get a speedy resolution is to ask Rich (who
has done the majority of the work on this) to clarify any aspects of the CP
that you find incoherent or vague.

--
with regards

Steve Faulkner
Technical Director - TPG

www.paciellogroup.com | www.HTML5accessibility.com |
www.twitter.com/stevefaulkner
HTML5: Techniques for providing useful text alternatives -
dev.w3.org/html5/alt-techniques/
Web Accessibility Toolbar -
www.paciellogroup.com/resources/wat-ie-about.html