- From: Aaron Leventhal <aleventhal@google.com>
- Date: Wed, 06 Sep 2017 17:09:14 +0000
- To: Joanmarie Diggs <jdiggs@igalia.com>
- Cc: ARIA Working Group <public-aria@w3.org>
- Message-ID: <CA+1LECTfoOFsY3vo+YGuvU4c+oVB0dWyBuq+Q+Ddy1C8WdZPGg@mail.gmail.com>
Sure thing, I will open an issue. Also, I care more about knowing the ultimate intention here than whether it actually happens in 1.1. Aaron On Wed, Sep 6, 2017 at 12:33 PM Joanmarie Diggs <jdiggs@igalia.com> wrote: > Hey Aaron. > > I'd have to do a bit of research to figure out if this was a deliberate > decision or some sort of oversight. > > Having said that, making such a change to the ARIA spec cannot be done > during the 1.1 timeframe. Therefore, would you mind opening an issue in > github against the ARIA spec so we can add it to our 1.2 TODO list? > > Thanks! > --joanie > > On 09/06/2017 12:01 PM, Aaron Leventhal wrote: > > 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 > > <mailto: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 <mailto: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 <mailto: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 17:09:49 UTC