[Bug 11239] Canvas support accessible caret tracking independent of Focus Ring tracking

http://www.w3.org/Bugs/Public/show_bug.cgi?id=11239

--- Comment #45 from Rich Schwerdtfeger <schwer@us.ibm.com> 2011-05-09 16:06:46 UTC ---
A major I have with Ian's latest patch is that it removes notification of the
point of regard for managed descendants of the focused element that was
provided for in the chair's decision.

After meeting with Maciej, the general issue is that although the proposed
changes to drawFocusRing() would work for both focused elements and
activedescendants (managed descendents) for drawing the "point of regard" it
would be clearer to separate the functionality of drawing a the active
descendant into a separate method. This, for example, would be clearer to Mac
developers. 

This issue, combined with the fact that there are issues raised with
canDrawCustom that prevents a magnifier from being notified that I have raised
to the chairs
(http://lists.w3.org/Archives/Public/public-html/2011Apr/0394.html), that if we
were to apply the new method now and the changes Ian's changes to drawFocusRing
that it would obfuscate the issues we are having with canDrawCustom. I would
like to note that I have added clarity on the points I made to the decision in
the change proposal as seen here:
http://lists.w3.org/Archives/Public/public-html/2011Apr/0423.html

Therefore, I would ask that:

- Ian apply the deltas described in
http://lists.w3.org/Archives/Public/public-html/2011Apr/0657.html to
drawFocusRing and setCaretSelectionPos 
- Maciej open a separate bug on drawFocusRing to separate out rendering of the
activedescendant point of regard.I will develop a change proposal and review it
with Maciej.

I am OK with Ian's changes to acquiring the blink period.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

Received on Monday, 9 May 2011 16:06:53 UTC