Remove input as a superclass of scrollbar and select

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.

Author: joanmarie

aria/aria.html

@@ -5676,7 +5676,6 @@ <h5 id="role-presentation-ednote-none">Editorial Note regarding the ARIA 1.1 <rr
 							<ul>
 								<li><rref>composite</rref></li>
 								<li><rref>group</rref></li>
-								<li><rref>input</rref></li>
 							</ul>
 						</td>
 					</tr>
@@ -5842,7 +5841,6 @@ <h5 id="role-presentation-ednote-none">Editorial Note regarding the ARIA 1.1 <rr
 					<tr>
 						<th class="role-parent-head" scope="row">Superclass Role:</th>
 						<td class="role-parent"><ul>
-							<li><rref>input</rref></li>
 							<li><rref>range</rref></li>
 						</ul></td>
 					</tr>