Bug 158415 - "Undo" has no effect on a chart when it's not on edit mode any more
Summary: "Undo" has no effect on a chart when it's not on edit mode any more
Status: RESOLVED DUPLICATE of bug 62595
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
7.6.3.2 release
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-11-28 10:37 UTC by David García
Modified: 2023-11-28 10:53 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
Video to show the issue (1.98 MB, video/mp4)
2023-11-28 10:37 UTC, David García
Details

Note You need to log in before you can comment on or make changes to this bug.
Description David García 2023-11-28 10:37:31 UTC
Description:
If you're editing a chart and then you click outside the chart to finish the editing, so you can resume your work on your cells, the "Undo" feature doesn't apply to the changes you've just made on your chart.

Steps to Reproduce:
1. You click on "Edit" on your chart.
2. You make some changes on your chart.
3. You click outside the chart to finish the editing, so you can keep working on your cells.

Actual Results:
If you click on Edit > Undo, because you have realized the changes on your chart weren't fine, the feaure is either not available or it only applies to the changes you've made on the cells.

Expected Results:
The "Undo" feature should work on all the changes you make on your sheets, whether they affect your cells or your charts.


Reproducible: Always


User Profile Reset: No

Additional Info:
Version: 7.6.3.2 (X86_64) / LibreOffice Community
Build ID: 29d686fea9f6705b262d369fede658f824154cc0
CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: Skia/Raster; VCL: win
Locale: es-ES (es_ES); UI: en-GB
Calc: CL threaded
Comment 1 David García 2023-11-28 10:37:51 UTC
Created attachment 191076 [details]
Video to show the issue
Comment 2 m_a_riosv 2023-11-28 10:53:59 UTC

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