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 129944 - Find dialog will not flash error message for invalid or end of page or not found strings.
Find dialog will not flash error message for invalid or end of page or not...
Status: RESOLVED OBSOLETE
Product: yelp
Classification: Applications
Component: General
2.3.x
Other Linux
: Normal normal
: ---
Assigned To: Shaun McCance
Yelp maintainers
AP3
Depends on:
Blocks:
 
 
Reported: 2003-12-24 12:17 UTC by Chandrashekhar. Korlahalli
Modified: 2006-07-22 15:26 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Patch for case 1 (1.26 KB, patch)
2004-03-04 11:04 UTC, cs_is 		none Details | Review

Description Chandrashekhar. Korlahalli 2003-12-24 12:17:07 UTC 
Find dialog in help browser will not flash any error dialog for invalid 
string or string not found or end of page string not found etc.

With the following steps. problem can be reproduced.

1. start gnome desktop, start gnopernicus & wait till you hear the sound.

2. start help browser, press Alt + E + F, find dialog box opens.

3. enter invalid or non existing string in the combo box.

4. Press next, now it has not found any string,  but, there is no error 
dialog flashed.

Expected:

1. Find operation should flash when ever it come acrss the following 
incidents.
a. for invalid text / string.
b. for string not found.
c. end of page


case 2:

after finding the string / text on help browser page, that text / string 
gets selected. but it will not send the event message to the screen reader.

Expected:

Selected string / text should be read by the screen reader.

Note: Pam filing 2 problems together as case 2 & case 1. Pls. let me know 
if they are 2 seperate bugs. I will  create seterate bug.
Comment 1 Calum Benson 2004-01-23 17:18:11 UTC 
I think these are probably separate.  Case 1 is really just a general
usability issue for everyone, not specifically an accessibility bug.

Marking AP3 on the basis of case 2.
Comment 2 cs_is 2004-03-04 11:04:56 UTC 
Created attachment 25156 [details] [review]
Patch for case 1
Comment 3 cs_is 2004-03-22 07:44:25 UTC 
For case 2: Is it required to report every time as a string matches 
as "string found" as no other modules does so
Comment 4 Chandrashekhar. Korlahalli 2004-03-22 08:45:34 UTC 
In my view,  when it finds  a match, the matched string should be 
sent to screen reader. Otherwise, for blind user it is  dificult  to  
know that there is a string match occured.Hence, I feel it is 
necessary to send all events to screen reader all the time.
Comment 5 Calum Benson 2004-10-21 16:47:46 UTC 
Apologies for spam-- ensuring Sun a11y team are cc'ed on all current a11y bugs.
 Filter on "SUN A11Y SPAM" to ignore.
Comment 6 Calum Benson 2006-04-26 17:15:59 UTC 
Apologies for spam... ensuring Sun a11y folks are cc'ed on all current accessibility bugs.
Comment 7 Don Scorgie 2006-06-11 09:37:20 UTC 
Is this still relevant with the new findbar Yelp now uses?

Currently, when an invalid string is entered, yelp acts the same as epiphany and (on my machine at least) emits a system beep.

Patch is obsolete (as the find dialog is no longer used)
Comment 8 Don Scorgie 2006-07-22 15:26:00 UTC 
No update.  Closing as OBSOLETE.  If the bug is still relevant, please reopen or add a comment.

Thanks