W3C home > Mailing lists > Public > public-aria@w3.org > September 2017

Re: Default values for aria-valuemin/max on role="progressbar"

From: Aaron Leventhal <aleventhal@google.com>
Date: Wed, 06 Sep 2017 16:01:48 +0000
Message-ID: <CA+1LECS5XwwaQ-S9Ceow4jo7wvA7npGcnJAuzY7SOXRGqZPN1Q@mail.gmail.com>
To: Alexander Surkov <surkov.alexander@gmail.com>
Cc: ARIA Working Group <public-aria@w3.org>
FWIW, I like the idea of supporting the 0/100 min/max for progressbar,
because it's one less special case in our code. No need to make things more
complex than necessary.

Aaron

On Wed, Sep 6, 2017 at 12:00 PM Aaron Leventhal <aleventhal@google.com>
wrote:

> 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:02:21 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 6 September 2017 16:02:22 UTC