Re: aria-rowindex and aria-colindex

If list consists of several groups of items, for example, when list items
are separated by separators, aria-setsize makes sense on list item because
there's no other proper place for it. Otherwise aria-setsize on list item
is a rather weird thing imo. Anyway I don't think that possible
inconsistency of rowindex/colindex on row and posinset on list items is
issue here, after all the inconsistency depends on what you think the grid
equivalent for list item is, is it a row or is it a cell. If all we need to
address spreadsheets use case then aria-rowstartindex and
aria-colstartindex on row element should be easy and nice solution for the
web developer.

By the way what should the table interface return for indexes pointing to
no cell? It seems "no cell" concept is something new for table interface
implementations/consumers.

On Tue, Jan 13, 2015 at 12:05 PM, Dominic Mazzoni <dmazzoni@google.com>
wrote:

> On Tue, Jan 13, 2015 at 7:22 AM, Alexander Surkov <
> surkov.alexander@gmail.com> wrote:
>
>> Is there a reason to provide rowindex/colindex on cells, it seems like
>> having them on role row should be enough to fit #2 use case?
>>
>
> It seems a little inconsistent if we *only* allowed them on role row,
> because aria-posinset and aria-setsize are basically the equivalent
> 1-dimensional concept for lists, and they're only allowed on the list item
> and not the list itself.
>
>
>>
>> Thanks.
>> Alex.
>>
>>
>>>
>>> One other thought: it'd be nice if you could put aria-rowindex on the
>>> element with role="row" rather than needing to repeat it on every single
>>> cell. (Not sure about aria-colindex, but at least the row would be helpful.)
>>>
>>> On Mon, Jan 12, 2015 at 5:07 PM, Daniel Trebbien <dtrebbien@gmail.com>
>>> wrote:
>>>
>>>> Hi Alexander,
>>>>
>>>> Two reasons that I can think of for having aria-rowindex/aria-colindex
>>>> in addition to rowspan/colspan are:
>>>>
>>>> 1.  You can apply aria-rowindex/aria-colindex to non-TD/TH elements.
>>>>
>>>> 2.  Even when using table elements, if you only have rowspan/colspan
>>>> available, then you have to make sure that the table model is "filled out"
>>>> to match the table that you are trying to represent.  For example, suppose
>>>> that you want to start at row 1000 of 5000.  You would have to have an
>>>> empty TD spanning the first 999 rows in a separate TBODY so that implied
>>>> empty rows would be created.  With aria-rowindex/aria-colindex, the
>>>> separate TBODY would be unnecessary.
>>>>
>>>>
>>>> On Mon, Jan 12, 2015 at 11:51 AM, Alexander Surkov <
>>>> surkov.alexander@gmail.com> wrote:
>>>>
>>>>> Hi. Can anybody share some use cases for aria-rowindex/colindex? Does
>>>>> it serve for other proposes than HTML rowspan/colspan attributes?
>>>>> Thanks.
>>>>> Alex.
>>>>>
>>>>
>>>>
>>>
>>
>