W3C home > Mailing lists > Public > public-canvas-api@w3.org > October to December 2011

Re: Request to re-open issue 131

From: Richard Schwerdtfeger <schwer@us.ibm.com>
Date: Tue, 25 Oct 2011 17:40:47 -0500
Cc: chuck@jumis.com, cyns@exchange.microsoft.com, franko@microsoft.com, mjs@apple.com, Paul Cotton <Paul.Cotton@microsoft.com>, public-canvas-api@w3.org, public-canvas-api-request@w3.org, public-html-a11y@w3.org, Sam Ruby <rubys@intertwingly.net>
Message-ID: <OF17B33C4E.A201ACFE-ON86257934.007C63D7-86257934.007C956E@us.ibm.com>

Maciej,

You agreed to provide feedback on my change proposal for this a couple
weeks ago. Have you had a chance to do that? I have not seen anything on
the list.

Cheers,
Rich

Rich Schwerdtfeger
CTO Accessibility Software Group



From:	Richard Schwerdtfeger/Austin/IBM@IBMUS
To:	Sam Ruby <rubys@intertwingly.net>, Paul Cotton
            <Paul.Cotton@microsoft.com>, mjs@apple.com,
            public-canvas-api@w3.org, public-html-a11y@w3.org,
Cc:	franko@microsoft.com, chuck@jumis.com,
            cyns@exchange.microsoft.com
Date:	10/25/2011 11:03 AM
Subject:	Request to re-open issue 131
Sent by:	public-canvas-api-request@w3.org



Paul,

Per your request. I would like to request that the chairs reopen issue 131.


In the chair's decision on issue 131 (
http://lists.w3.org/Archives/Public/public-html/2011Apr/0270.html)

- The chairs did not have adequate information as to the definition of a
text Baseline property supplied in text metrics.
- The removal of canDrawCustom was not adopted even though it was possible
for an author draw a custom focus ring without it matching the actual path
provided to drawFocusRing.

 We would like to reopen this issue for the following reasons:

- We will provide a change proposal that includes the additional
information needed to define the text baseline and because after
discussions with developers, such as Tab Atkins, it was agreed it would be
of tremendous value to have the text baseline to compute focus rings around
text rendered on the canvas.
- I spoke with Maciej at the Apple campus after the decision and he felt it
would be better for developers to have two separate API for drawing focus
rings. One would be for drawing a focus ring that took on the standard
platform drawing conventions for a focus ring and a separate custom focus
ring that would allow an author to draw a custom focus ring but still drive
magnification features in the browser.
- I would like to bring our spec. closer to WhatWg which attempted to
separate out drawFocusRing into two methods for the reasons Maciej stated.
Ian had made those changes to the WhatWG spec. after also speaking with
Maciej.


http://lists.w3.org/Archives/Public/public-html-a11y/2011Jul/0123.html


Rich Schwerdtfeger



graycol.gif
(image/gif attachment: graycol.gif)

Received on Tuesday, 25 October 2011 22:41:24 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 25 October 2011 22:41:25 GMT