|
Rich, I don't have Excel but I can tell you what happens in Calc 3.1... Test case - merge top three cells in second column. 1) Start with focus on upper left cell, shift right once, three cells in first column become selected, second column (one spanned cell) is selected, shift arrow again, now only three cells are selected (the upper left, the spanned, and the top cell in the third column. This feels inconsistent, though I can see their logic. 2) Start with focus on the cell below the top cell in the first column, shift right once, same behavior as above, shift right again, only two cells are selected (the starting cell and the cell in the third column in the second row). To be consistent I would think everything in the upper left 3x3 would be selected. 3) Start with focus on the cell in the first column and third row, same behavior as #2. The behavior is Writer 3.1 is different and the behavior in Symphony is again different. So we have two choices for IATable's un/selectRow/Column (4 methods) 1) Define what the behavior should be. 2) Specify that it is determined by the app. Do you have a recommendation? --
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:
|
Alexander
Surkov ---07/08/2009 12:18:21 AM---Hi. IA2 doc doesn't address
situation when row or column spans are
_______________________________________________ Accessibility-ia2 mailing list [email protected] https://lists.linux-foundation.org/mailman/listinfo/accessibility-ia2
