Dominic,
Everything in Canvas is clipped to the canvas area. It does not mean the
bounds of the object will change in accessibility services any more than we
clip content in the browser window.
I don't see clipping due to higher z-order drawing.
Rich
Rich Schwerdtfeger
From: Dominic Mazzoni <dmazzoni@google.com>
To: robert@ocallahan.org
Cc: Rik Cabanier <cabanier@gmail.com>, Jatinder Mann
<jmann@microsoft.com>, Richard Schwerdtfeger/Austin/IBM@IBMUS,
"Rik Cabanier (cabanier@adobe.com)" <cabanier@adobe.com>, Jay
Munro <jaymunro@microsoft.com>, "Philippe Le Hegaret
(plh@w3.org)" <plh@w3.org>, Canvas <public-canvas-api@w3.org>,
Alexander Surkov <surkov.alexander@gmail.com>
Date: 01/10/2014 01:23 AM
Subject: Re: drawSystemFocusRing and drawCustomFocusRing names are
confusing.
On Thu, Jan 9, 2014 at 5:14 PM, Robert O'Callahan <robert@ocallahan.org>
wrote:
On Fri, Jan 10, 2014 at 2:08 PM, Rik Cabanier <cabanier@gmail.com> wrote:
Why not? If we cache the path, we should be able to draw the focus on
top of the canvas.
Because there might be other content on top of the rendering of the
focused element, that should not be obscured by the focus ring. Or the
focused element might be supposed to be clipped.
Are we overoptimizing for obscure theoretical cases? What are the chances
someone wants to draw a *system* focus ring but clip it and overlay other
elements on top of it? We can provide a good native focus ring.
I wonder if there aren't just as many plausible use cases where the focus
ring would naturally extend outside of the canvas bounds, and it'd be
unnatural and annoying for the author to enlarge the canvas just for focus
rings.
