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 438675 - Firefox: multi-item accessibles inhibit mode changing/navigation
Firefox: multi-item accessibles inhibit mode changing/navigation
Status: RESOLVED FIXED
Product: lsr
Classification: Deprecated
Component: extensions
unspecified
Other Linux
: Normal normal
: 0.5.3
Assigned To: Scott Haeger
LSR maintainers
Depends on:
Blocks: 431344
 
 
Reported: 2007-05-15 17:45 UTC by Scott Haeger
Modified: 2007-05-24 15:31 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Scott Haeger 2007-05-15 17:45:35 UTC
Mode changing and navigation past a 'multi-item accessible' is awkward because the user must go to the last item, change modes, and then navigate out of the accessible.  An example of this can be seen in multiline textboxes and the radio button grouping in forms.html.  Ideally, we want to be able to navigate past the accessible from any item within the accessible.
Comment 1 Scott Haeger 2007-05-23 21:02:22 UTC
The container functions are to be used to get past multi-item accessibles.  I included entries in the list of containers and am now checking the task_por to see if it is a container.  This solved most of problems I have seen except the radio buttons.  I will try to solve this problem and will do more testing before this bug is closed.
Comment 2 Peter Parente 2007-05-24 11:45:38 UTC
Radio buttons will appear as individual elements, possibly even spread across containers. Without the use of the member of relation, I'm not sure if there is a way for you to properly determine that the next/prev radio button is in the same set as the current one. There's no "set id" that groups them.

It would be nice to treat them as a set. I'm just saying you might need to be creative or ask Aaron to provide more information on radio buttons than what they currently provide.
Comment 3 Scott Haeger 2007-05-24 15:31:29 UTC
All cases that I have come across work good.  In the future, more roles may need to be added to CONTAINERS_BY_ROLE.  

Radio button groupings pose a challenge for the reasons Peter points out in comment #2.  A separate bug has been issued that addresses this specific problem.  http://bugzilla.gnome.org/show_bug.cgi?id=440965