Bug 76278 - [EDITING][FIELD][UNDO] Updated user field does not respond to undo command
Summary: [EDITING][FIELD][UNDO] Updated user field does not respond to undo command
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.2.2.1 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Undo-Redo Fields
  Show dependency treegraph
 
Reported: 2014-03-17 16:51 UTC by Gergely Rácz
Modified: 2024-01-14 03:12 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gergely Rácz 2014-03-17 16:51:54 UTC
Steps to reproduce:

1. Insert a User defined field in a Writer (Insert->Fields->Others...->Variables->User Field)
2. Edit the inserted field (write some text in it).
3. Push Ctrl+Z 

Results

The inserted field does not change.

Expected Results

The inserted field should undo the update of the field.

Fact

This issue does not appears any of the other fields (I have tested).

When you use the Undo command, it shows that the Undo command has ran (the redo button is available). If you give the command again it will delete the inserted field.
Comment 1 sophie 2014-03-18 16:52:28 UTC
Confirmed, the undo/redo indicate 'Modified field' - set as New, change OS to all Version: 4.2.3.1
Build ID: 3d4fc3d9dbf8f4c0aeb61498a81f91c5b7922f13 Ubuntu 13.10 - Sophie
Comment 2 Joel Madero 2015-05-02 15:41:26 UTC Comment hidden (obsolete)
Comment 3 Gordo 2015-06-17 20:28:47 UTC
Still reproducible.

Windows Vista 64
Version: 4.4.4.2
Build ID: f784c932ccfd756d01b70b6bb5e09ff62e1b3285

Version: 5.1.0.0.alpha1+
Build ID: 46564fd97308ce070248482ad65a311a329a2b76
TinderBox: Win-x86@39, Branch:master, Time: 2015-06-15_00:08:53
Comment 4 QA Administrators 2016-09-20 10:01:05 UTC Comment hidden (obsolete)
Comment 5 János Néhrer 2016-09-21 02:58:18 UTC
Still reproducible.

Windows 8.1 x86-64
Version: 5.2.1.2
Build ID: 31dd62db80d4e60af04904455ec9c9219178d620
Comment 6 Xisco Faulí 2017-09-29 08:49:08 UTC Comment hidden (obsolete)
Comment 7 János Néhrer 2017-09-29 09:29:28 UTC
Issue is quite reproducible with Version: 5.4.1.2 (x64)
Build ID: ea7cb86e6eeb2bf3a5af73a8f7777ac570321527
CPU threads: 4; OS: Windows 6.29; UI render: default; 
Locale: hu-HU (en_US); Calc: group

Well it turned even worse (updating a user defined field that was changed to Text format will reset the format to 'Standard'). But that's another bug...
Comment 8 QA Administrators 2018-09-30 02:48:17 UTC Comment hidden (obsolete)
Comment 9 János Néhrer 2018-10-08 05:12:06 UTC
Still reproducible

Version: 6.1.2.1 (x64)
Build ID: 65905a128db06ba48db947242809d14d3f9a93fe
CPU threads: 4; OS: Windows 6.3; UI render: default; 
Locale: hu-HU (en_US); Calc: group threaded
Comment 10 sdc.blanco 2020-01-12 22:43:55 UTC
Can reproduce that undo will not change an updated User Field variable, but will undo an updated Variable.

Version: 6.5.0.0.alpha0+ (x64)
Build ID: 035c7717c135c66c0ec025500b73ae9c13b7c586
CPU threads: 8; OS: Windows 10.0 Build 18363; UI render: GL; VCL: win; 
Locale: da-DK (en_DK); UI-Language: en-US
Calc: threaded
Comment 11 QA Administrators 2022-01-12 03:42:04 UTC Comment hidden (obsolete)
Comment 12 sdc.blanco 2022-01-13 12:58:22 UTC
reproduce -- cannot undo User field  (additional information:  cannot undo "Input field" either)

Version: 7.4.0.0.alpha0+ (x64) / LibreOffice Community
Build ID: bb29b12a9e367d181a5d9d962d466df41e093e0c
CPU threads: 8; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win
Locale: da-DK (da_DK); UI: en-US
Calc: CL
Comment 13 QA Administrators 2024-01-14 03:12:25 UTC
Dear Gergely Rácz,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug