https://bugs.documentfoundation.org/show_bug.cgi?id=95357
Michael Büker <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #3 from Michael Büker <[email protected]> --- I can confirm this for 5.1.1.3 on Linux/x64. I'm seeing this bug in documents that come out of Microwoft Word, both .doc and .docx format, but also when merging such documents into my own .odt files with the "Compare document" tool. Example: Let's say the sentence "Mary had a little DOG." was changed to "Mary had a little lamb." The change will show in Writer like this: > Mary had a little lambDOG. (with "lamb" as an insertion change and "DOG" crossed out as deletion change) Now, when I navigate changes with the "Next Change" and "Previous Change" buttons to and reach the insertion of "lamb", the word "lamb" gets selected. I can click "Accept Change", which will accept the insertion of "lamb". But it will then *not* select the deletion change of "DOG", but skip right over it, taking me to the next change in a whole other sentence, leaving the deletion change of "DOG" hanging and forcing me to go back manually. This also happens when navigating to the "lamb" change and then right-clicking the selected "lamb" change and clicking "Accept Change" in the contect menu. It does *not* happen when I right-click directly into the word "lamb" without navigating to it with the "Next Change" or "Previous Change" button, in which case the word "lamb" is not selected when I click "Accept Change" in the contect menu. It also does *not* happen when I place the cursor, with my mouse or keyboard, into the word "lamb", but don't have it selected before opening the contect menu or using the toolbar to select "Accept Change". MY BEST GUESS as to what happens is this: Whenever the internal "jump to change" mechanism is used and selects a change directly adjacent to another one, accepting (or rejecting!) the thusly selected change skips the adjacent one. It does not happen for all cases when the change was selected in a different, manual way (like selecting with the mouse, placing the cursor etc.). I can perfectly reproduce this behaviour, so in case you can't follow my clumsy description, I'm willing to make a GIF or something ;) -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Libreoffice-bugs mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
