[Issue 124959] Table: Selection inconsistence for merged cells

[bu...@apache.org]

https://bz.apache.org/ooo/show_bug.cgi?id=124959

Kaji <kc...@my.fit.edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kchinzorig2012@my.fit.edu

--- Comment #3 from Kaji <kc...@my.fit.edu> ---
Configuration:
OS: Windows 10 Pro (64-bit)
Hardware: 16GB of ram, Intel I75820k 
Version: AOO420m1 (Build:9800)  -  Rev. 1692551

First I was able to first replicate the bug with sample document provided. 
For the tests that follow I used a new document each time.

Test 1: (Vertical cells merging) 
      -    Created an 8 x 8 table in writer. (Actual table is 9 x 9 but the top
row and left column are used for numbering, as to make it easier to read)
      -    Combined 3 cells from (5, 2) to (5, 4) 
      -    Tried selecting (1, 2) to (5, 4), this leads to expected results:
the cells (1, 3) to (4, 4) are not selected. 
      -    This time I tried selecting (1, 4) to (5, 2). This in theory selects
the same rectangle as I tried before. But this time it selects everything
including previously not selected cells. 

Test 2: (Horizontal cell merging) 
      -    Created the same table as in test 1.
      -    Merged cells from (3, 4) to (5, 4)
      -    Selecting cells from (2, 2) to (5, 4) selects the entire rectangle. 

Test 3:
      -    Created the same table as in test 1.
      -    This time I tried merging different number of cells vertically. I
tested ranges 2 to 8, but the behavior seems consistent across all of them.
      -    I will describe a test I did with 4 merged cells. In this case it
was cells from (4, 1) to (4, 4)
      -    I selected cell (8, 8) for being non adjacent to the merged cell. 
      -    Then I selected the merged cell by mouse.
      -    I tried navigating the table with arrow keys at point. 
      -    When selection came by mouse from a non-adjacent cell, movements to
either side resulted in selecting the topmost adjacent cells on either side. In
this case (3, 1) and (5, 1).
      -    However if I selected the merged cell with arrow keys from adjacent
cell to either of its side it “remembers” it. More specifically the row it got
selected from. 
      -    Navigating to either side from this point onward selects the same
row. For example:
      -    If I was on cell (3, 2) 
      -    Then moved right to the merged cell using the arrow keys. 
      -    Then tried to move right again using the arrow keys. The cell that
gets selected is (4, 2).
      -    This happens on every cell adjacent to the right or left of the
vertically merged cell. 

Test 4:
Was done with same principle as test 3 but to test horizontally merged cells.
The difference I have found is that when trying to navigate up or down from
horizontally merged cell with arrow keys it always moves you up or down to the
center of all adjacent cells on that side. For Example:
      -    Same table as properties as in test 1.
      -    Merged cells from (3, 3) to (5, 3)
      -    Select non-adjacent cell with mouse
      -    Select merged cell
      -    Move up or down with arrow keys
      -    The selected cells will be (4, 3) or (4,5)
      -    Navigate to cell (3, 3) with arrow keys or mouse
      -    Move down to the merged cell with arrow keys
      -    Move back up. Selected cell is (4, 3).
For navigating up or down from a horizontally merged cell selects the center
cell in every case and moves accordingly (in case of even number of merged
cells it takes the right of the two cells in the center). While navigating
horizontally from a vertically merged cell depends on how the cell was selected
in the first place. If selected from either sides it remembers the row, if from
top/bottom or any non-adjacent cell it will simply select the topmost cell.

Test 5:
      -    Same table as in test 1
      -    Merged cells from (4, 1) to (4, 6)
      -    Selected cells from (2, 1) to (5,1)
      -    Selected cells from (2, 1) to (5,2)
      -    Selected cells from (2, 1) to (5,3)
      -    In every case it selects the correct number of rows on either side
of the merged cell. The merged cell is also selected. (Screenshot included:
Test5_A)

Test 6:
Same principle as in test 5 with horizontally merged cells. Observed same
results as in test 5. (Screenshot included: Test6_A)
Comments:
I was able to confirm the inconsistency present in selecting merged tables.
>From what I can tell horizontally merged cells seem to be more consistent with
selection.

-- 
You are receiving this mail because:
You are the assignee for the issue.