After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 701831 - Search entry lacks an accessible name
Search entry lacks an accessible name
Status: RESOLVED DUPLICATE of bug 706014
Product: gnome-documents
Classification: Core
Component: general
3.8.x
Other Linux
: Normal normal
: ---
Assigned To: GNOME documents maintainer(s)
GNOME documents maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2013-06-07 23:11 UTC by Joanmarie Diggs (IRC: joanie)
Modified: 2013-09-03 17:48 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
event listener (224 bytes, text/x-python)
2013-06-07 23:12 UTC, Joanmarie Diggs (IRC: joanie)
Details

Description Joanmarie Diggs (IRC: joanie) 2013-06-07 23:11:49 UTC
Steps to reproduce:
1. Launch the attached accessible event listener in a terminal
2. Give focus to GNOME Documents
3. Type any character (which move focus to the search entry)

Expected results: The entry would have an accessible name like "Search"

	object:state-changed:focused(1, 0, 0)
		source: [text | Search] <<<<
		host_application: [application | gnome-documents]

Actual results: The entry lacks an accessible name

	object:state-changed:focused(1, 0, 0)
		source: [text | ] <<<<
		host_application: [application | gnome-documents]

Impact: Orca just says "text" as a result of the focus change; presenting "Search text" (or something to that effect) would better inform the user of the focus change.
Comment 1 Joanmarie Diggs (IRC: joanie) 2013-06-07 23:12:24 UTC
Created attachment 246286 [details]
event listener
Comment 2 Debarshi Ray 2013-09-03 17:35:00 UTC
Isn't this a duplicate of bug 706014 ?
Comment 3 Joanmarie Diggs (IRC: joanie) 2013-09-03 17:48:14 UTC
Looks like it. All I can say is, premature senility sucks. :P (And apologies)

*** This bug has been marked as a duplicate of bug 706014 ***