Closed Bug 374722 Opened 17 years ago Closed 9 years ago

ARIA menubar fixes (support owns, remove superfluous menu objects?)

Categories

(Core :: Disability Access APIs, defect)

defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: aaronlev, Unassigned)

References

(Blocks 2 open bugs)

Details

(Keywords: access)

We need two things:
1) owns should affect menu events, the menu hierarchy no longer needs proper parenting
2) The hierarchy should be exposed with the correct objects and roles in ATK

The right way to fix #2 is to probably have the same thing at all times for menus in nsIAccessible, and have our ATK impl eat the extra menu popup objects. Yeech!
Summary: ARIA menubar fixes → ARIA menubar fixes (support owns, remove superfluous menu objects?)
Blocks: fox3access
Flags: wanted1.9.2?
OK let's see if I understand. At the nsIAccessible layer, we have these 'extra' menu popup objects... are they only considered 'extra' in the ATK impl?  Is there an orca bug or something for background?
(In reply to comment #1)
> OK let's see if I understand. At the nsIAccessible layer, we have these 'extra'
> menu popup objects... are they only considered 'extra' in the ATK impl? 
Correct.

> Is
> there an orca bug or something for background?
I don't think so. It's not considered a bug in Orca. At one point there was a bug in Mozilla about having redundant menu objects in Mozilla.
I want steps to reproduce.

Joanmarie, do you guys work around this currently?
Traditional menu bar in Gtk:

   menu bar
      File (menu)
          New (menu item)
          Open... (menu item)
          ...
      Edit (menu)
          Cut (menu item)
          Copy (menu item)
          ....
      View (menu)
          ... (menu items)

Note that menu bars contain menus which in turn contain menu items.

Examples I found:
(http://wiki.codetalks.org/wiki/index.php/Set_of_ARIA_Test_Cases#Menubar_and_Menu)

1. http://developer.yahoo.com/yui/examples/menu/menuwaiaria_source.html

   menu bar
       section
           File (menu item)
       section
           Edit (menu item)

Upon opening the Edit menu I see another accessible gets created:

     menu bar
       section
           File (menu item)
       section
           Edit (menu item)
           Edit (menu)
               Section
                   Undo (menu item)
                   Redo (menu item)
                   ...

2. http://codetalks.org/source/widgets/grid/grid.html

   menu bar
       section
           Edit (menu item)
       section
           View (menu item)
       ...

Upon opening the Edit menu I see another accessible gets created:

   menu bar
       section
           Edit (menu item)
           (nameless) (menu)
               Cut (menu item)
               Copy (menu item)
               ...
       section
           View (menu item)
       ...

3. http://archive.dojotoolkit.org/nightly/dojotoolkit/dijit/tests/test_Menu.html

   menu bar
       File (menu item)
       Edit (menu item)
       ...
   
Upon opening the Edit menu I see another accessible gets created, though elsewhere in the hierarchy.

   menu bar
       File (menu item)
       Edit (menu item)
       ...

   ...
   (nameless) (menu)
       Cut Ctrl+X (menu item)
       Copy Ctrl+C (menu item)
       ...

Orca seems to be coping with this well enough. It's not what we'd expect to see in a proper menu bar, but.... <shrug>

Hopefully this is what you are looking for David.(??)
(In reply to comment #4)
> Hopefully this is what you are looking for David.(??)

Thanks!

Anyone understand comment #0 (part 1)? Aaron?
Mass un-assigning bugs assigned to Aaron.
Assignee: aaronleventhal → nobody
It would be nice to catch an idea how what we can change on Firefox side to improve usability of these DHTML menus.
Please reopen if there is a concrete next step for this bug (and please state it).
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Resolution: FIXED → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.