- From: Aaron Leventhal <aleventhal@google.com>
- Date: Wed, 06 Sep 2017 16:00:54 +0000
- To: Alexander Surkov <surkov.alexander@gmail.com>
- Cc: ARIA Working Group <public-aria@w3.org>
Received on Wednesday, 6 September 2017 16:01:30 UTC
Although it can be indeterminate, that is a separate issue for aria-valuenow. It it would still make sense to have a valuemin/max, with a default of 0 to 100. The indeterminate state can still be specified even with a min/max, and the indeterminate state is likely temporary until more progress is made. Aaron On Wed, Sep 6, 2017 at 11:55 AM Alexander Surkov <surkov.alexander@gmail.com> wrote: > The only difference between those I can think of is a progressbar may be > indeterminate, which mix/max are not applied to. Not sure if that's a case > here. > > On Tue, Sep 5, 2017 at 11:21 PM, Aaron Leventhal <aleventhal@google.com> > wrote: > >> While implementing aria-valuemax recently, we noticed that aria-valuemin >> and aria-valuemax do not default to "0" and "100" on progressbar. >> >> All of the other range sliders .. scrollbar, separator and slider, all >> have these default values. >> >> Was this accidentally left out, or on purpose? >> >> Aaron >> > >
Received on Wednesday, 6 September 2017 16:01:30 UTC