Closed Bug 1033283 Opened 7 years ago Closed 7 years ago
_PRESSED on menu buttons
Currently, we don't expose the pressed state on xul:button or xul:toolbarbutton of type "menu", as used in the web console. This bug was uncovered by the patch for bug 977273. We transform the role to a toggle button with the HASPOPUP state, but don't expose the pressed state.
I'd like to take a crack at this.
Athena, in testing your patch, I actually fixed this one. It is a one-line test in code, but needs some tests added. I just got back from lunch and am testing my tests and will attach a patch shortly. Sorry for "stealing" this one! :)
One-line fix, and I added tests for the role and states.
Assignee: nobody → marco.zehe
Status: NEW → ASSIGNED
Attachment #8449368 - Flags: review?(surkov.alexander)
Hah, no problem! I did take a look (before my dinner ;)), and I was way off base. I'll just look around for another one.
Comment on attachment 8449368 [details] [diff] [review] Expose pressed state on menu buttons, too Review of attachment 8449368 [details] [diff] [review]: ----------------------------------------------------------------- ::: accessible/generic/Accessible.cpp @@ +1581,5 @@ > } > } > > // special case: A native button element whose role got transformed by ARIA to a toggle button > + // Also applies to togglable button menus, like in the Dev Tools Web Console nit: two spaces between 'button' and 'menus', dot in the end ::: accessible/tests/mochitest/states/test_aria.xul @@ +3,5 @@ > +<?xml-stylesheet href="chrome://mochikit/content/tests/SimpleTest/test.css" > + type="text/css"?> > + > +<window xmlns="http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul" > + title="Accessible XUL toggle button state tests"> nit: it'd bet good to keep it more generic
Attachment #8449368 - Flags: review?(surkov.alexander) → review+
Landed with nits addressed: https://hg.mozilla.org/integration/mozilla-inbound/rev/62eec1dede89
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla33
You need to log in before you can comment on or make changes to this bug.