Closed Bug 363697 Opened 15 years ago Closed 5 years ago

Implement action to programmatically show menu for textfields and buttons

Categories

(Core :: Disability Access APIs, defect)

x86
All
defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: hwaara, Unassigned)

References

(Blocks 2 open bugs)

Details

(Keywords: access, Whiteboard: [auto-closed:inactivity])

I know there was talk about implementing a way to programmatically show the menu of buttons (ROLE_COMBOBOX), but I'm having trouble finding the relevant bugs, so filing this for easier tracking.

- mozPopupbuttonAccessible (which maps to ROLE_COMBOBOX) needs this for its ShowMenu action to work.

- autocomplete widgets and other textfields with a popup would also benefit from an action to programmatically show the menu.
For user, the shortcut for Windows and Linux is shift+F10, for Mac OS X is ctrl+space.

Current code for showing context menu is,
Windows:
http://lxr.mozilla.org/seamonkey/source/widget/src/windows/nsWindow.cpp#4741
GTK2:
http://lxr.mozilla.org/seamonkey/source/widget/src/gtk2/nsWindow.cpp#2145
Mac:
http://lxr.mozilla.org/seamonkey/source/widget/src/mac/nsMacEventHandler.cpp#1136
(In reply to comment #1)

Something like that, but it needs to be accessible via nsIAccessible, as an action.
Blocks: keya11y
Keywords: access
I guess every element of COMBOBOX role should have child acessible element of PUSHBUTTON role, that element has nsIAccessible::DoAction() method which shows popup. What do you about?
(In reply to comment #3)
> I guess every element of COMBOBOX role should have child acessible element of
> PUSHBUTTON role, that element has nsIAccessible::DoAction() method which shows
> popup. What do you about?

What about other buttons with a popup? What if COMBOBOX's internal structure changes? What about custom widgets that use this role (possibly via W3C roles, if possible)?

The point is that it is really fragile to depend on how a specific role's internal structure looks.
(In reply to comment #4)

> The point is that it is really fragile to depend on how a specific role's
> internal structure looks.
> 

(In reply to comment #2)
> (In reply to comment #1)
> 
> Something like that, but it needs to be accessible via nsIAccessible, as an
> action.
> 

Then at least it shouldn't be in nsIAccessible. Probably new interface if you wish.
Blocks: xula11y
No longer blocks: keya11y
Mass un-assigning bugs assigned to Aaron.
Assignee: aaronleventhal → nobody
AUTO-CLOSED. This bug untouched for over 2000 days. Please reopen if you can confirm the bug and help it progress.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → INCOMPLETE
Whiteboard: [auto-closed:inactivity]
You need to log in before you can comment on or make changes to this bug.