Closed Bug 1556047 Opened 6 years ago Closed 5 months ago

MSAA event_system_menupopupend not fired when ARIA menu styled to display:none

Categories

(Core :: Disability Access APIs, defect, P3)

Product:
Core
Component:
Disability Access APIs
Version:
67 Branch
Type:
defect

Tracking

()

Status:
RESOLVED DUPLICATE of bug 682811

People

(Reporter: aaronlev, Assigned: eeejay)

References

(Blocks 1 open bug)

Details

(Keywords: papercut)

Attachments

(1 file)

Test case file
2.04 KB, text/html
Details
Attached file Test case file —

Steps:

  1. Launch screen reader and MSAA accevent watcher from MSAA SDK tools
  2. Listen to menu events (Options ->settings)
  3. Load attached test file
  4. Navigate to button and hit Enter
  5. Notice that menu opens and menupopupstart is fired
  6. Press escape
  7. Notice the menu closes but menupopupend is not fired

This doesn't seem to affect JAWS or NVDA usage, but it still seems like a bug.
Note that Chrome is not firing either event, which is a known bug being worked on.

The priority flag is not set for this bug.
:Jamie, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(jteh)
Blocks: aria
Flags: needinfo?(jteh)
Priority: -- → P3
Severity: normal → S3
Depends on: 682811

This is a problem for screen readers if a menu item hasn't yet been focused. STR (with NVDA):

  1. Open this test case:
    data:text/html,<body onkeydown="if (event.key == 'Escape') menu.hidden = true;"><button onclick="menu.hidden = false;">show</button><div id="menu" hidden role="menu"><div role="menuitem">a
  2. Press the button. Observe that NVDA says "menu".
  3. Press escape.
    • Expected: NVDA should say: "Show button"
    • Actual: NVDA says nothing.
  4. Press NVDA+tab.
    • Expected: NVDA should say: "Show button focused"
    • Actual: NVDA says: "unknown defunct"
Keywords: papercut
Assignee: nobody → eitan

The patch I submitted to bug 682811 should fix this. will wait for it get resolved before closing this as dup.

The test case in comment 0 seems to be broken now. I can confirm that this is fixed with the STR in comment 2, though.

Status: NEW → RESOLVED
Closed: 5 months ago
Duplicate of bug: 682811
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: