Bug 142982 - EDITING Grammar check blue underline does not disappear with track changes enabled
Summary: EDITING Grammar check blue underline does not disappear with track changes en...
Status: RESOLVED DUPLICATE of bug 36540
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Track-Changes
  Show dependency treegraph
 
Reported: 2021-06-22 12:35 UTC by NISZ LibreOffice Team
Modified: 2023-12-02 06:11 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
Example file from Writer (13.29 KB, application/vnd.oasis.opendocument.text)
2021-06-22 12:35 UTC, NISZ LibreOffice Team
Details
Screenshot of the problem in Writer with changes visible (143.07 KB, image/png)
2021-06-22 12:35 UTC, NISZ LibreOffice Team
Details
Screenshot of the problem in Writer with changes hidden (15.16 KB, image/png)
2021-06-22 12:35 UTC, NISZ LibreOffice Team
Details

Note You need to log in before you can comment on or make changes to this bug.
Description NISZ LibreOffice Team 2021-06-22 12:35:07 UTC
Created attachment 173080 [details]
Example file from Writer

This is a followup to bug 66043
If there is a grammar error in a document marked by blue squiggly line, and change tracking is enabled, fixing the grammar error does not make the blue squiggly line disappear.

Steps to reproduce:
    1. Open attached file
    2. The grammar error (double spaces between words) marked by blue squiggly lines was corrected with change tracking enabled.

Actual results:
The blue line is visible in the first paragraph, both with visible and hidden tracked changes.
In the second paragraph an insertion created a grammar error (double comma), that is highlighted correctly both with visible and hidden changes.

Expected results:
The blue line should disappear whether the changes are hidden or not if the changes would be fixing that grammar error.

LibreOffice details:
Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community
Build ID: 2a7e64da7f385de8dbba1802530e251cf29259fb
CPU threads: 4; OS: Windows 10.0 Build 18363; UI render: default; VCL: win
Locale: hu-HU (hu_HU); UI: en-US
Calc: CL
Comment 1 NISZ LibreOffice Team 2021-06-22 12:35:38 UTC
Created attachment 173081 [details]
Screenshot of the problem in Writer with changes visible
Comment 2 NISZ LibreOffice Team 2021-06-22 12:35:54 UTC
Created attachment 173082 [details]
Screenshot of the problem in Writer with changes hidden
Comment 3 Dieter 2021-07-07 19:46:14 UTC
I confirm it with

Version: 7.1.4.1 (x64) / LibreOffice Community
Build ID: f67b1ddedeb24fca1c5938e7cebfab73d708b35b
CPU threads: 4; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win
Locale: de-DE (de_DE); UI: en-GB
Calc: threaded
Comment 4 Márcio Sena 2022-04-02 22:06:04 UTC
Problem remains on version:

Version: 7.3.2.2 (x64) / LibreOffice Community
Build ID: 49f2b1bff42cfccbd8f788c8dc32c1c309559be0
CPU threads: 4; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win
Locale: pt-BR (pt_BR); UI: pt-BR
Calc: CL
Comment 5 Mike Kaganski 2023-12-02 06:11:44 UTC

*** This bug has been marked as a duplicate of bug 36540 ***