Open Bug 1864240 Opened 2 years ago Updated 1 year ago

Investigate if widget-overflow panel in Synced Tabs Menu in Customizable UI needs to be updated to pass a11y_checks

Categories

(Firefox :: Settings UI, task, P3)

task

Tracking

()

People

(Reporter: ayeddi, Unassigned)

References

Details

There is a failing test in the browser/components/customizableui/test/browser_synced_tabs_menu.js that appear to, in some environments, send a click event on a panel button while the panel itself is still in the showing state.

We should wait for the panel to be shown to keep the test harness happy and to ensure the test is proceeding as it is expected to. Similar behavior was unpacked during the investigation of the bug 1859035 and bug 1863815.

a11y_checks failing data (with stack trace):

FAIL	browser/components/customizableui/test/browser_synced_tabs_menu.js	Node is not accessible via accessibility API	PanelUI-remotetabs-connect-device-button	toolbarbutton	PanelUI-remotetabs-button	"
chrome://mochikit/content/browser-test.js:test_ok:1583
chrome://mochikit/content/tests/SimpleTest/AccessibilityUtils.js:a11yFail:339
chrome://mochikit/content/tests/SimpleTest/AccessibilityUtils.js:assertCanBeClicked:658
chrome://mochikit/content/tests/SimpleTest/AccessibilityUtils.js:runIfA11YChecks/this.AccessibilityUtils:635
chrome://mochikit/content/tests/SimpleTest/AccessibilityUtils.js:handleClick:751
chrome://mochitests/content/browser/browser/components/customizableui/test/browser_synced_tabs_menu.js:null:223
chrome://mochikit/content/browser-test.js:handleTask:1134
chrome://mochikit/content/browser-test.js:_runTaskBasedTest:1206
chrome://mochikit/content/browser-test.js:Tester_execTest:1348
chrome://mochikit/content/browser-test.js:nextTest/<:1123
chrome://mochikit/content/tests/SimpleTest/SimpleTest.js:SimpleTest.waitForFocus/<:1058"

Update: so far I was not able to confirm that the panel is not yet shown (i.e. try run with the log output that the panel is open), so this issue needs further investigation.

Assignee: ayeddi → nobody
You need to log in before you can comment on or make changes to this bug.