GNOME Bugzilla – Bug 363079
Gok can not UI Grab scrollbar in yelp.
Last modified: 2007-11-22 03:00:23 UTC
Please describe the problem: The scrollbar in yelp can not be grabbed by gok. Steps to reproduce: 1. Start GOK 2. Start Yelp 3. With yelp focused select UI GRAB in the gok window. Actual results: Gok can not UI Grab scrollbar in yelp. Expected results: Gok can UI Grab scrollbar in yelp. Does this happen every time? Yes. Other information: This bug is reproducible with gok1.2.0 and gnome2.16.
Tim, sorry I missed this earlier. Can you try at-poke on the scrollbar and tell me the accessible name, and state set?
David, it's OK for you have noticed this bug. :) The problem is the vertical scroll bar is not visible in at-poke. It's odd.
I'm assigning this bug to Yelp since the scrollbar should probably be made to expose the state: 'VISIBLE'. I'm not sure why this isn't happening automatically.
I believe the issue is that yelp is now using gecko for content, and we aren't getting the vertical scroll bar from gecko.
>I believe the issue is that yelp is now using gecko for content, and we aren't >getting the vertical scroll bar from gecko. Probably true. What version of gecko is being used? If we can confirm that the scrollbars are not exposing the necessary states, we should move this bug to mozilla and close this one as NOTGNOME.
Thanks for the bug report. There is already a bug report about this against yelp (bug #355696), which has been marked as a duplicate of The Infamous A11y Bug of Yelp (bug #157941). I'm marking this a duplicate of bug #355696. I recently tested yelp against gecko 1.9 and found the majority of our a11y problems solved (not solved in the 1.8 brnach), but I didn't check the scrollbar. I'll test when I get home. FWIW, this should be marked as NOTGNOME and opened in mozilla bugzilla if it isn't already known as the scrollbars are gecko constructs (Unless it's already solved in 1.9, in which case, its probably a special case of bug #157941). *** This bug has been marked as a duplicate of 355696 ***
Is this a known issue of Gecko a11y? https://bugzilla.mozilla.org/show_bug.cgi?id=285167
I think it's true.