Great! Thank you.
On Mon, Jul 13, 2009 at 11:38 PM, Pete Brunet<[email protected]> wrote: > Alex, Since you and Rich are in agreement I will write it up that way. I am > editing the full list of changes to IATable, i.e. IATable2, and will send > that out a little later. -Pete > > Alexander Surkov wrote: > > Hi, Pete. > > It looks like Excel behaviour is the same as I suggested (based on > Rich tests). So I'm happy because this behaviour looks like reasonable > behaviour for me because when author selects the row then he doesn't > know where is origin of the cell. Therefore selection shouldn't depend > on the spanned cell's origin. That's Excel does. > > Alex. > > > On Mon, Jul 13, 2009 at 10:44 PM, Pete Brunet<[email protected]> wrote: > > > Rich, I think my son has a copy of Excel. Let me check it for its > consistency when I can get access to his machine. BTW, Alex says that FF > has no means to select rows and columns so that is why he wants to know what > behavior to implement. Based on that, the options for the IA2 spec would > be: > > 1) Implement it as defined in the IA2 spec irregardless of the native > behavior. > 2) Implement to mimic the app's GUI behavior; if there is no GUI behavior, > implement it as defined in the IA2 spec. > > I'll give my best guess at what the IA2 spec's definition of behavior should > be after I try Excel. > > -- > Pete Brunet > > a11ysoft - Accessibility Architecture and Development > (512) 238-6967 > pete @ a11ysoft.com > http://www.a11ysoft.com/about/ > http://www.linkedin.com/in/petebrunet > Ionosphere: WS4G > > Richard Schwerdtfeger wrote: > > 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 ---07/08/2009 10:40:25 AM---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-depend > > Andres Gonzalez <[email protected]> > Sent by: [email protected] > > 07/08/2009 10:38 AM > > To > Alexander Surkov <[email protected]>, > "[email protected]" > <[email protected]>, "[email protected]" > <[email protected]> > 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 > > > _______________________________________________ > 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 > > _______________________________________________ Accessibility-ia2 mailing list [email protected] https://lists.linux-foundation.org/mailman/listinfo/accessibility-ia2
