Bug 166718 - Value for Height in the Position and Size parameters for a shape is empty
Summary: Value for Height in the Position and Size parameters for a shape is empty
Status: RESOLVED FIXED
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Draw (show other bugs)
Version:
(earliest affected)
24.2.3.2 release
Hardware: Other macOS (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-05-25 09:57 UTC by Alex
Modified: 2025-05-27 14:44 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 Alex 2025-05-25 09:57:02 UTC
Description:
Selecting a shape after scrolling frequently leaves the Position and Size parameter values blank.

Steps to Reproduce:
1. Click the page to select nothing.
2. Scroll left/right or up/down.
3. Click a shape and observe the Properties sidebar's Position and Size parameters.
(4.) As it randomly seems to work as expected, please repeat the previous steps if necessary.


Click one or more other shapes to eventually have all fields populated with values.

Actual Results:
Some or all of the fields "Position X", "Position Y", "Width" and "Height" are left blank.

Expected Results:
All value fields of "Position X", "Position Y", "Width" and "Height" should contain values.


Reproducible: Sometimes


User Profile Reset: Yes

Additional Info:
Only scrolling seems to provoke this issue; zooming does not. Having a shape selected before scrolling also seems to prevent this issue.

---

Version: 24.2.3.2 (AARCH64) / LibreOffice Community
Build ID: 433d9c2ded56988e8a90e6b2e771ee4e6a5ab2ba
CPU threads: 8; OS: macOS 14.5; UI render: Skia/Metal; VCL: osx
Locale: de-DE (en_DE.UTF-8); UI: en-US
Calc: threaded
Comment 1 Jeremy Norvell 2025-05-25 21:57:10 UTC
Thank you for reporting the bug. I can confirm that the bug has been observed in the version 25.2 of LibreOffice listed below.

Specifically I see that the "Height" value seems to show blank fairly consistently. It showed a value prior to scrolling and then selecting the shape.

Version: 25.2.3.2 (X86_64) / LibreOffice Community
Build ID: bbb074479178df812d175f709636b368952c2ce3
CPU threads: 8; OS: macOS 15.2; UI render: Skia/Raster; VCL: osx
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded

I was not able to reproduce this behavior on an updated release. It may be worth updating to see if that fixes it.

Version: 25.8.0.0.alpha1+ (X86_64) / LibreOffice Community
Build ID: 84da1f50ca8261129909901c2ff72adb9c67510a
CPU threads: 8; OS: macOS 15.2; UI render: Skia/Raster; VCL: osx
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded
Comment 2 Alex 2025-05-26 12:43:51 UTC
Thanks for your quick response! I've updated to version 25.2 and can confirm that it occurs "only" for the height attribute now.
Comment 3 Buovjaga 2025-05-27 04:23:32 UTC
(In reply to Alex from comment #2)
> Thanks for your quick response! I've updated to version 25.2 and can confirm
> that it occurs "only" for the height attribute now.

Per what Jeremy said, can you try with a master build: https://dev-builds.libreoffice.org/daily/master/current.html
Comment 4 Saburo 2025-05-27 14:37:48 UTC
It seems like this commit.

Version: 25.8.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 1dd45462fd55ba2069b1303f8713a591ef57feab
CPU threads: 12; OS: Windows 11 X86_64 (build 26100); UI render: Skia/Vulkan; VCL: win
Locale: ja-JP (ja_JP); UI: en-US
Calc: CL threaded

author	Pranam Lashkari
commit 1dd45462fd55ba2069b1303f8713a591ef57feab

svx: avoid emptying sidebar properties
these properties are either updated or reformatted based on *Blanked variables so no need to do an extra update

problem:
emptying these properties causes to lose measurement units in LOK. It happens due to second time this sidebar is not completly initialised but just updated the value of the fields so units are lost for LOK.

Change-Id: Id32638686578652ab4ffa25a638b5308c46eea2b
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/179583
Comment 5 Buovjaga 2025-05-27 14:44:09 UTC
Thanks for finding the fix, Saburo-san. Let's close as fixed as we know the commit.