RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1438179 - Revision tracking: insertion-deletion couple is not recognized and LO skips over the deletion part
Summary: Revision tracking: insertion-deletion couple is not recognized and LO skips o...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libreoffice
Version: 7.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Caolan McNamara
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-04-01 16:06 UTC by Matěj Cepl
Modified: 2020-07-13 13:41 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-07-13 13:41:04 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
screencast of the issue (317.62 KB, video/webm)
2017-04-01 16:06 UTC, Matěj Cepl
no flags Details
screencast of the current state (819.84 KB, video/webm)
2017-04-15 08:58 UTC, Matěj Cepl
no flags Details
Screencast from reproducing the bug in libreoffice-5.3.6.1-23.el7 (428.94 KB, application/octet-stream)
2019-09-19 09:35 UTC, Pavlin Georgiev
no flags Details

Description Matěj Cepl 2017-04-01 16:06:47 UTC
Created attachment 1268130 [details]
screencast of the issue

Description of problem:
See the situation when going through the revisions in this document. I have a couple <ins>I</ins><del>We</del>. I jump to this couple and LO selects just "I" insertion. When I accept it, it jumps automatically to next revision behind it, so it effectively skips over the deletion of "We".

Version-Release number of selected component (if applicable):
libreoffice-writer-5.0.6.2-7.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Put cursor somewhere before the insertion/deletion couple
2. Jump to the next change
3. Accept change

Actual results:
see above, only the insertion is accepted and cursor jumps to the next pair, effectively skipping over the deletion.

Expected results:
Either LO should recognize the couple as one unit, and accept/reject it as whole, or at least when accepting just insertion/deletion, it should immediately select the member of the pair.

Additional info:

Comment 4 Michael Stahl 2017-04-12 20:19:39 UTC
fixed in upstream master commit 25eb0899227830cca7f28006376962d84f8e9c7a
upstream libreoffice-5-3 for release 5.3.3 commit 644aacd1e4b419f2f85b6c2e18026ca04206b378
upstream libreoffice-5-2 for release 5.2.7 commit 224073a5002df33da673a63db24c19f5a43143c1

added the patch to Fedora f24 and f25

but it is probably a bit late to get it into RHEL-7.4 now

Comment 5 Fedora Update System 2017-04-14 09:23:33 UTC
libreoffice-5.2.6.2-6.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2017-b10faf327b

Comment 6 Caolan McNamara 2017-04-14 09:27:34 UTC
made this available via CSB experimental repo

Comment 7 Red Hat Bugzilla Rules Engine 2017-04-14 09:27:41 UTC
Development Management has reviewed and declined this request. You may appeal this decision by reopening this request.

Comment 8 Fedora Update System 2017-04-15 00:29:01 UTC
libreoffice-5.2.6.2-6.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-b10faf327b

Comment 9 Matěj Cepl 2017-04-15 08:58:40 UTC
Created attachment 1271775 [details]
screencast of the current state

OK, the situation is certainly better and technically speaking this bug has been fixed, it is now possible to go through text and process revisions just with shortcut keys.

However, it would be even more convenient if LO was able to recognize insert/delete pairs and go through them as such.

Comment 11 Pavlin Georgiev 2019-09-19 09:35:44 UTC
Created attachment 1616649 [details]
Screencast from reproducing the bug in libreoffice-5.3.6.1-23.el7

TEST SETUP
Distro: RHEL-7.8-20190912.3
Component version: libreoffice-5.3.6.1-23.el7


TEST PROCEDURE
1. Create a text file in LibreOffice writer by taking contents
   from LibreOffice's help.
2. Select menu Edit->Track Changes->Record.
3. Make several modifications in the text and save.
4. Exit LibreOffice writer.
5. Start LibreOffice writer.
6. Reopen the most recent file.

Accepting changes cannot be done via mouse clicks.
See attached screencast.


RESULT
The bug is still present in version: 5.3.6.1-23.
I do not accept the using of key combinations as solution to the bug.


Note You need to log in before you can comment on or make changes to this bug.