ACTION-1677: Remove input as a superclass of scrollbar and select

Remove input as a superclass of scrollbar and select

Joanmarie Diggs
Due on:
November 5, 2015
Created on:
July 7, 2015
Associated Issue:
Related emails:
No related emails

Related notes:

1. The other superclass of scrollbar is range. A range is a widget
representing a range of values that can be set by the user. This
describes scrollbar adequately.

2. In the case of select, making a selection from a set of choices
does not necessarily mean a widget is an input field. A menu is
a select; not an input. Widgets which are both (e.g. listbox) can
subclass both.

3. At the moment, input does not have any unique supported states
and properties to be inherited by subclasses. However that could
change. For instance, perhaps required and/or readonly would be
appropriate properties for all inputs. Scrollbars and some of the
subclasses of select (like menu) cannot be readonly or required.

Done in this commit:

Setting the state to "pending review". Two-line change.

Joanmarie Diggs, 7 Jul 2015, 21:48:41

Setting status back to Open and postponing due date for two months as per the 3 Sept 2015 ARIA concall.

Joanmarie Diggs, 3 Sep 2015, 16:51:21

Done as per the 28 Jan ARIA concall:

Setting state to CLOSED.

Joanmarie Diggs, 28 Jan 2016, 19:27:07

Display change log.

James Nurthen <>, Valerie Young <>, Chairs, Daniel Montalvo <>, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <>.
$Id: 1677.html,v 1.1 2023/05/22 16:31:50 carcone Exp $