https://bugs.documentfoundation.org/show_bug.cgi?id=42535

--- Comment #10 from ikjt <[email protected]> ---
The original report is very confusing and describes a special case of an issue
I've run into several times within just a few hours of using LibreOffice.

Simply put: after a Cut/Paste/Delete operation, keyboard navigation is utterly
broken.

Now, I don't know who LibreOffice tries to cater to, but I'm amazed this kind
of bug can exist for years. Advanced users need keyboard navigation to work!

Allow me to summarize the research:

* After Paste, if you try to modify the selection using
Shift+Up/Down/Left/Right, the other end of the selection will unexpectedly jump
to A1 (bug 57008, bug 68703, bug 87388).

* After Paste, if you try to modify the selection using Shift+Cmd+Down or
Shift+Cmd+Right, the other end of the selection will unexpectedly jump to
column A or row 1 (this bug). It may be more complicated than that — I haven't
tested this extensively.

* After Paste, if you try to move to the next (but not previous) value in the
column/row by hitting Cmd+arrow, the movement will overshoot by an amount
that's based on the original cursor location (bug 62436).

* After Cut/Delete, if you try to move to the next *or* previous value in the
column/row by hitting Cmd+arrow, the movement will over-/undershoot by an
amount that's based on the size and direction of the prior selection (bug
95730).

It has been conjectured that all of these are in fact the one and the same bug.
Perhaps. But it should be noted that the "Move to block margin" command can
miscalculate the coordinates in three different ways depending on whether
you're simultenously modifying a selection and whether the previous operation
was Paste or Cut/Delete.

Also, when the selection is being modified, even basic Up/Down/Left/Right
navigation is enough to trigger the jump to A1, so it's not just about "Move to
block margin".

However, if these are indeed various manifestations of the same faulty
arithmetic, then fixing it would likely be fairly easy and yield a huge payoff
for the effort in terms of usability.

For now, I'm going back to the increasingly obsolete OpenOffice because it's
just more usable.

I have tested recent and 3.3.0 versions of both LibreOffice and OpenOffice.
LibreOffice has always had this bug, OpenOffice never.

-- 
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Libreoffice-bugs mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

Reply via email to