Steps to reproduce: 1. Load data:text/html,<div role="link" aria-current="page">1</div> 2. Use Accerciser to examine the element Expected results: the element would be exposed with STATE_ACTIVE Actual results: the element is not exposed with STATE_ACTIVE https://rawgit.com/w3c/aria/master/core-aam/core-aam.html#ariaCurrent
Hopefully it goes without saying, but just in case: In addition to exposing STATE_ACTIVE, when the value of aria-current changes from non-false to false or from false to non-false, an object:state-changed:active event should also be fired.
Assignee: nobody → jdiggs
Status: NEW → ASSIGNED
Attachment #8883124 - Flags: review?(mzehe)
(This version fixes a nit in the previous version's alphabetizing of states. Sorry for the noise!)
Comment on attachment 8883136 [details] [diff] [review] proposed patch r=me.
Attachment #8883136 - Flags: review?(mzehe) → review+
Pushed by firstname.lastname@example.org: https://hg.mozilla.org/integration/mozilla-inbound/rev/4bc42c671bd2 Elements with a defined, non-false value for aria-current should expose ATK_STATE_ACTIVE. r=marcoz
You need to log in before you can comment on or make changes to this bug.