Rich, That is correct.
I'll work on it some more tomorrow (Monday).
Pete
Richard Schwerdtfeger wrote:
Just to make sure, A new accessible table interface is being
created - like an IA2Table2 - correct? We don't want to break the
existing implementations that use it like Symphony and ATV support for
it.
Rich
Rich Schwerdtfeger
Distinguished Engineer, SWG Accessibility Architect/Strategist
 Pete Brunet
---07/09/2009 10:14:29 PM---Alex, That sounds good. -Pete
Alex, That sounds good. -Pete
Alexander Surkov wrote:
That should be reasonable and expected
behaviour from user point of
view I think. So we could follow it to implement selectRow/Column
methods of IAccessibleTable. However we need to clarify what "unselect
other rows" means here. Eventually we need to unselect all cells in
other rows that aren't spanned to selected row somehow. So we should
have something like:
selectRow - selects all cells in the given row including cells spanned
on this row and unselects every cell in other rows excluding cells
spanned on this row.
Alex.
On Fri, Jul 10, 2009 at 12:17 AM, Pete Brunet<[email protected]> wrote:
Thanks Alex,
I think we need to add a method to select a single cell. What do others
think?
We need to determine what is the correct behavior when spanned cells
exist.
I think the proper behavior is as follows. I'll use an example.
Otherwise,
it's hard to describe. Let's take a 3x3 table with the three cells in
the
middle column merged. If focus is on any of the cells in the first
column,
pressing shift right arrow once should select the starting cell plus the
spanning cell and pressing shift right arrow one more time should add
the
new cell in the last column but only the one in the same row as the
starting
cell. Both Symphony 1.2 and OOo 3.0.1 are buggy and inconsistent
depending
on which row you start selecting from. I'll try Symphony 1.3 and OOo
3.1
later today.
Does anyone have a differing idea of proper behavior?
Pete
Alexander Surkov wrote:
So, Pete. I mean there is no GUI to select row as it defined by IA2
(i.e. select this row and unselect others), but every row can be
selected by cells and unselected by cells. If AT needs shortcut for
this (note IA2 doesn't provide method to select single cell) then I
think it's worth to implement it.
Conflict is if we will treat selectRow as the following. We should
select every cell in the row and unselect every cell in other rows.
Since one and the same cell can be shared between two different rows
then this is conflict. I mean what should we do? Should we select or
should we unselect that cell? (I think the formal case which is select
and then unselect it doesn't make sense.) IA2 should provide
documentation where meaning of the method can't be treated by
different ways.
Alex.
On Thu, Jul 9, 2009 at 1:02 PM, Pete Brunet<[email protected]> wrote:
Alex, If you can't select rows or columns from the GUI what do you think
about just returning E_NOTIMPL for those methods?
Also I think nether method documentation nor implementation should be
self
conflicting.
I agree, but did you have an example in mind where the documentation and
implementation would conflict?
Pete
Alexander Surkov wrote:
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
_______________________________________________
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
|
