W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > July 2010

[Bug 10249] Canvas requires a content selection method

From: <bugzilla@jessica.w3.org>
Date: Wed, 28 Jul 2010 17:06:07 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1OeA51-0001cK-Gj@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10249





--- Comment #1 from Rich Schwerdtfeger <schwer@us.ibm.com>  2010-07-28 17:06:07 ---
This is related to Issue 74. Currently, the HTML accessibility task force is
proposing an API that authors would use to report the selection position to a
browser when editing text. This would be used by the user agent to support
accessibility services to drive magnification during content selection. 

This approach requires an additional work by the author. It would be better if
the author have a method to draw a highlighted selection of content on the
canvas in such a way as to also support screen magnifiers. This method would
need to report the current selection position to assistive technology using
accessibility services layers for each platform. Windows allows for caret
tracking so this position would drive a caret tracking. This would also be the
case for UNIX systems. On the Mac selected text is processed differently and
the current selection position (the position you are pointing at during a
selection drag must be reported to assistive technologies). 

As a minimum the new method should take an element that pertains to the element
having the caret in the fallback content or if Charles McCathieneville's
proposal is accepted an element in an area map.

It must be possible for the user agent to assess the coordinates used to draw
the selection. This can be done by either using the drawing path or by passing
a
rectangle with coordinates. Carets often very in width and style. For example,
they may be drawn using with a blinking rectangle that inverts the fill area of
the rectangle. 

The severity is marked as normal. However if the proposed setCaretSelectionRect
method is not adopted as as part of Issue 74. This becomes a blocker.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Wednesday, 28 July 2010 17:06:12 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:30:52 UTC