[Webkit-unassigned] [Bug 27048] New: [Gtk] Implement STATE_FOCUSED, STATE_FOCUSABLE, and corresponding events for text objects
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Tue Jul 7 16:30:07 PDT 2009
https://bugs.webkit.org/show_bug.cgi?id=27048
Summary: [Gtk] Implement STATE_FOCUSED, STATE_FOCUSABLE, and
corresponding events for text objects
Product: WebKit
Version: 528+ (Nightly build)
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: Normal
Priority: P2
Component: Accessibility
AssignedTo: webkit-unassigned at lists.webkit.org
ReportedBy: joanmarie.diggs at gmail.com
CC: xan.lopez at gmail.com, William.Walker at sun.com,
apinheiro at igalia.com
According to: http://library.gnome.org/devel/atk/stable/atk-AtkState.html:
~~~
ATK_STATE_FOCUSABLE
Indicates this object can accept keyboard focus, which means all events
resulting from typing on the keyboard will normally be passed to it when it has
focus
ATK_STATE_FOCUSED
Indicates this object currently has the keyboard focus
~~~
While I typically think of "focusable" being akin to "I can Tab to it," it
seems to be used to mean "the active object." Thus we expect objects which
implement the accessible text interface to have STATE_FOCUSABLE if the user can
interact with the object via keyboard and STATE_FOCUSED if the user is
interacting with the object. The corresponding events (focus: and
object:state-changed:focused) are also expected.
WebKit objects of ROLE_TEXT lack these states and events.
While I can work around the absence of these things in some cases, there are
other cases in which one needs to know if an object has focus. Example:
distinguishing caret navigation related object:text-caret-moved and
object:text-selection-changed events from the same events seen when using
Epiphany's Find toolbar.
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the webkit-unassigned
mailing list