Bug 152350 - Changes to name and value of custom document property lost when resizing dialog
Summary: Changes to name and value of custom document property lost when resizing dialog
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
6.0.0.3 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: bibisected, bisected, regression
Depends on:
Blocks: File-Properties
  Show dependency treegraph
 
Reported: 2022-12-02 10:14 UTC by Nikk
Modified: 2025-07-05 03:11 UTC (History)
5 users (show)

See Also:
Crash report or crash signature:


Attachments
place error (12.01 KB, image/png)
2022-12-02 10:17 UTC, Nikk
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Nikk 2022-12-02 10:14:51 UTC
Description:
when editing document properties, the changes made in the fields are completely reset to the original ones when the editing window is resized. Is it possible to save the size of the editing window permanently between opening the program and restarting the computer?

Actual Results:
-

Expected Results:
-


Reproducible: Always


User Profile Reset: No

Additional Info:
[Information automatically included from LibreOffice]
Locale: ru
Module: TextDocument
[Information guessed from browser]
OS: Windows (All)
OS is 64bit: no
Comment 1 Nikk 2022-12-02 10:17:54 UTC
Created attachment 183951 [details]
place error
Comment 2 jcsanz 2022-12-02 21:19:17 UTC
I can confirm the error but:

- It occurs only with custom properties
- It occurs only with the last property added
- It only occurs when modify height but not with width 
- It doesn't occur if the property has been saved previously, i.e., the dialog has been closed previously

Versión: 6.4.7.2 (x64)
Id. de compilación: 639b8ac485750d5696d7590a72ef1b496725cfb5
Subprocs. CPU: 4; SO: Windows 10.0 Build 19045; Repres. IU: predet.; VCL: win; 
Configuración regional: es-ES (es_ES); Idioma de IU: es-ES
Calc: CL

Version: 7.5.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 1435c5b12646269e2b5b58ec7d51626dce6505db
CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win
Locale: es-ES (es_ES); UI: es-ES
Calc: CL threaded

Versión: 6.4.7.2 (x64)
Id. de compilación: 639b8ac485750d5696d7590a72ef1b496725cfb5
Subprocs. CPU: 4; SO: Windows 10.0 Build 19045; Repres. IU: predet.; VCL: win; 
Configuración regional: es-ES (es_ES); Idioma de IU: es-ES
Calc: CL
Comment 3 jcsanz 2022-12-02 21:54:05 UTC
Version: 7.4.2.3 / LibreOffice Community
Build ID: 40(Build:3)
CPU threads: 1; OS: Linux 5.15; UI render: default; VCL: kf5 (cairo+xcb)
Locale: es-ES (es_ES.UTF-8); UI: es-ES
7.4.2-2
Calc: threaded
Comment 4 BogdanB 2022-12-28 19:08:30 UTC
Repro
Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: b9e3e20bfd102880d12384892eaeca094c38a519
CPU threads: 16; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: ro-RO (ro_RO.UTF-8); UI: en-US
Calc: threaded
Comment 5 Stéphane Guillou (stragu) 2023-01-27 08:49:35 UTC
Regression, as not reproduced in:

Version: 5.3.3.2
Build ID: 3d9a8b4b4e538a85e0782bd6c2d430bafe583448
CPU Threads: 8; OS Version: Linux 5.15; UI Render: default; VCL: gtk2; Layout Engine: new; 
Locale: en-AU (en_AU.UTF-8); Calc: group

Using the linux-64-releases repo, I found the earliest release to have the issue was libreoffice-6.0.0.0.beta1

But slightly different symptoms: both name and value are lost on both vertical and horizontal resize.
Comment 6 raal 2023-01-28 08:52:08 UTC
This seems to have begun at the below commit.
Adding Cc: to Szymon Kłos ; Could you possibly take a look at this one?
Thanks
 87e376e795c82c77ea9859999111ebc892ff35c9 is the first bad commit
commit 87e376e795c82c77ea9859999111ebc892ff35c9
Author: Norbert Thiebaud <nthiebaud@gmail.com>
Date:   Wed Nov 8 05:21:40 2017 -0800

    source 272a96da03522a82db4185e7858d05375f3ea95e

https://git.libreoffice.org/core/+/272a96da03522a82db4185e7858d05375f3ea95e
Comment 7 Szymon Kłos 2023-01-31 07:34:24 UTC Comment hidden (obsolete)
Comment 8 QA Administrators 2025-07-05 03:11:16 UTC
Dear Nikk,

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