You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In working on the new meter role, I had it subclass range. The problem with that is range subclasses widget and a widget is interactive.
The general consensus from the Working Group's meeting today is that range should subclass structure. Then the interactive roles which subclass range should also subclass widget.
The text was updated successfully, but these errors were encountered:
Regarding the interactive roles, it turns out that slider and spinbutton already subclass both range and input. And, of course, input subclasses widget. So it's only progressbar and scrollbar whose parent class need to be changed.
This is needed to support the aria-value* attributes on non-interative,
and potentially static objects such as a meter.
Because range now subclasses structure, we need to use multiple inheritance
with the widget roles which subclass range. Those roles are: progressbar,
scrollbar, slider, and spinbutton. The latter two already subclass both range
and input thus no further change is needed. Progressbar and scrollbar now
subclass both range and widget.
Addresses github issue #892.
In working on the new
meter
role, I had it subclassrange
. The problem with that isrange
subclasseswidget
and awidget
is interactive.The general consensus from the Working Group's meeting today is that
range
should subclassstructure
. Then the interactive roles which subclassrange
should also subclasswidget
.The text was updated successfully, but these errors were encountered: