Bug 125707 - Tracking changes doesn't track changes inside textboxes (nor changes in page layout caused by it)
Summary: Tracking changes doesn't track changes inside textboxes (nor changes in page ...
Status: RESOLVED DUPLICATE of bug 49361
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.4.7.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Track-Changes Textbox
  Show dependency treegraph
 
Reported: 2019-06-05 11:55 UTC by Telesto
Modified: 2020-04-27 17:33 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
Example file (22.07 KB, application/vnd.oasis.opendocument.text)
2019-06-05 11:55 UTC, Telesto
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Telesto 2019-06-05 11:55:08 UTC
Description:
Tracking changes doesn't track changes inside textboxes (nor changes in page layout caused by it)

Steps to Reproduce:
1. Open the attached file
2. Enable record changes
3. Make edits inside the textbox (even expanding the textbox by pressing enter

Actual Results:
Nothing marked as changed

Expected Results:
Should work inside textboxes


Reproducible: Always


User Profile Reset: No



Additional Info:
Version: 6.4.0.0.alpha0+ (x86)
Build ID: 93477d1a963e38e3319013e43835a8ffef200972
CPU threads: 4; OS: Windows 6.3; UI render: default; VCL: win; 
TinderBox: Win-x86@42, Branch:master, Time: 2019-06-02_10:16:52
Locale: it-IT (nl_NL); UI-Language: en-US
Calc: threaded
Comment 1 Telesto 2019-06-05 11:55:28 UTC
Created attachment 151936 [details]
Example file
Comment 2 Dieter 2019-06-06 06:23:51 UTC
I confirm it with

Version: 6.3.0.0.beta1 (x64)
Build ID: a187af327633f5f00363be5131bd21a13e0f1a7b
CPU threads: 4; OS: Windows 10.0; UI render: default; VCL: win; 
Locale: en-US (de_DE); UI-Language: en-GB
Calc: threaded
Comment 3 NISZ LibreOffice Team 2020-04-27 17:33:24 UTC

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