Re: [css3-ui] nav-index <number> value

On Oct 18, 2012, at 7:49 AM, Yves Lafon <ylafon@w3.org> wrote:

> On Thu, 18 Oct 2012, Brad Kemper wrote:
> 
>> On Oct 17, 2012, at 9:57 AM, "Tab Atkins Jr." <jackalmage@gmail.com> wrote:
>> 
>>> On Wed, Oct 17, 2012 at 2:01 AM, Yves Lafon <ylafon@w3.org> wrote:
>>>> in [1], it says:
>>>> nav-index: auto | <number> | inherit
>>>> Then
>>>> <<
>>>> <number>
>>>>   The number (which is non-zero and positive) indicates the sequential
>>>>   navigation order for the element. '1' means first. Elements with the
>>>>   same nav-index value are navigated in document order when that
>>>>   nav-index value is being navigated.
>>>> If the first number non-zero and positive is '1', then the value is probably
>>>> <integer> and not a <number>.
>>>> Cheers,
>>>> 
>>>> [1] http://www.w3.org/TR/2012/WD-css3-ui-20120117/#nav-index0
>>> 
>>> Yup, you're right.
>> 
>> It would be better for authors if decimals could be used. So if there was already a 'nav-index:1' and a a 'nav-index:2', something could be inserted between them in the tab order with a 'nav-index:1.5'. Or before the first one with a 'nav-index:0.5'.
> 
> I don't mind if it's an <number> and not an <integer>, but in that case '1' should not be listed as the first possible value

Clearly. I meant for that to be implicate to my comments. The lowest positive number would be the first. 

> So either the text is amended, or the value type is amended...

Agreed. 

> ...Or else, authors should learn to increment their values by 10 in case they need to insert something later on (that will remind an old habit to some of you :) ).

Yeah, z-index was not fun that way. 

Also like z-index, where some authors pick enormous numbers in order to be on top, some will pick tiny decimals in order to be first in tab order. But I'm OK with that.

Received on Friday, 19 October 2012 00:21:36 UTC