I would mimic what excel does. I have found inconsistencies in OO and Symphony.
Rule:
- if you select a row you select all cells in that row
- If individual cells span cells in other rows you select the "affected
cells" in the other rows.
Rich
Rich Schwerdtfeger
Distinguished Engineer, SWG Accessibility Architect/Strategist
Andres Gonzalez
<[email protected]
om> To
Sent by: Alexander Surkov
accessibility-ia2 <[email protected]>,
[email protected] "[email protected]
nuxfoundation.org ation.org"
<[email protected]
ation.org>, "[email protected]"
07/08/2009 10:38 <[email protected]>
AM cc
Subject
Re: [Accessibility-ia2]
IAccessible::(un)selectRow/Column
method implementation
Alex: what about if these methods mimic what the user can do via the GUI
when selecting a row or column. It would be app-dependent.
Thanks,
--Andres.
--Andres.
> -----Original Message-----
> From: [email protected]
> [?mailto:[email protected]]
> On Behalf Of Alexander Surkov
> Sent: Tuesday, July 07, 2009 11:22 PM
> To: [email protected]; [email protected]
> Subject: Re: [Accessibility-ia2]
> IAccessible::(un)selectRow/Column method implementation
>
> Though if we won't select not origin cell then selectRow/Column won't
> select row or column entirely in some cases and isRow/ColumnSelected
> will return false. I'm not sure how is it correct. Opinions?
>
> Alex.
>
>
> On Wed, Jul 8, 2009 at 1:17 PM, Alexander
> Surkov<[email protected]> wrote:
> > Hi. IA2 doc doesn't address situation when row or column spans are
> > presented in a table. So let we have an example,
> >
> > <table>
> > <tr>
> > <td>cell1</td>
> > <td rowspan="1">cell2</td>
> > </tr>
> > <tr>
> > <td>cell3</td>
> > </tr>
> > </table>
> >
> > visually this table is presented like
> >
> > |---------|---------|
> > | cell1 | cell2 |
> > |---------| |
> > | cell3 | |
> > |---------|---------|
> >
> > If I select second row then we should select "cell3".
> Should we select
> > spanned "cell2" as well? On the one hand it looks reasonable because
> > when I want to select row then I want to see all cells in the row
> > selected. On another hand I would say no because we should unselect
> > first row per documentation and therefore we should uselect "cell1"
> > and "cell2", i.e. "cell2" remains unselected. So should we add words
> > into documentation (un)selectRow/Column deals with origin cells only
> > (i.e. cells those aren't result of row or column spans)?
> >
> > Alex.
> >
> _______________________________________________
> Accessibility-ia2 mailing list
> [email protected]
> https://lists.linux-foundation.org/mailman/listinfo/accessibility-ia2
>
_______________________________________________
Accessibility-ia2 mailing list
[email protected]
https://lists.linux-foundation.org/mailman/listinfo/accessibility-ia2
<<inline: graycol.gif>>
<<inline: pic28983.gif>>
<<inline: ecblank.gif>>
_______________________________________________ Accessibility-ia2 mailing list [email protected] https://lists.linux-foundation.org/mailman/listinfo/accessibility-ia2
