To Andres: Afaik HTML table is unique example of multiselectable table in Firefox where row or column spans are applicable and there is no GUI to select row or column of the HTML table. You can select cells (ctrl + click on the cell) one by one or cells all together (ctrl + click on the table border). So I don't know how I should implement selectRow/Column methods for Firefox's HTML tables. Also I think nether method documentation nor implementation should be self conflicting.
Alex. On Thu, Jul 9, 2009 at 11:26 AM, Pete Brunet<[email protected]> wrote: > There is different (and probably buggy) behavior if you compare the > behavior of multiple cell selection in Symphony and OOo, so the methods > should report what happens in the GUI, even mimicking buggy behavior. -Pete > > > Andres Gonzalez wrote: >> 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
