Consider removing the 'activedescendent' from the Reorderer, in light of new understanding of its purpose
Description
Discussions in the Fluid IRC channel on May 2, 2008 ( http://wiki.fluidproject.org/x/NYsk ) led to a new understanding of the purpose of the ARIA 'activedescendant' property, and the fact that it may not be appropriate for our purposes: it seems to be intended for the case where focus is not being put on to the descendant of a container (focus stays on the container itself), so you need a property to tell you which descendant is active. We do put focus on the descendant, and we already have another way of keeping track of which one is active, so we may simply not need it.
We should double-check the spec and the best practice guide, and decide whether or not to remove this property.
FF2, FF3, Opera 9.6, Safari 3.2 (Mac OS 10.5) FF3, IE7 (Win Vista)
Anastasia Cheetham March 24, 2009 at 6:06 PM
This fix looks, good, but I found one file that still mentions ariadescendent: /src/webapp/sample-code/keyboard-a11y/jquery-ui-tabs/jquery-ui-accessible-tabs.js
Discussions in the Fluid IRC channel on May 2, 2008 ( http://wiki.fluidproject.org/x/NYsk ) led to a new understanding of the purpose of the ARIA 'activedescendant' property, and the fact that it may not be appropriate for our purposes: it seems to be intended for the case where focus is not being put on to the descendant of a container (focus stays on the container itself), so you need a property to tell you which descendant is active. We do put focus on the descendant, and we already have another way of keeping track of which one is active, so we may simply not need it.
We should double-check the spec and the best practice guide, and decide whether or not to remove this property.