Description: UI: Unchecking relative width while keep Ratio Active, breaks image ratio Steps to Reproduce: 1. Open attachment 185930 [details] 2. Select the image and press F4 3. Position and size Tab 4. Check the Keep Ratio checkbox 5. Width: Check the Relative to checkbox 6. Uncheck the Relative to checkbox -> Height changes to 17 CM Actual Results: Image Ratio lost Expected Results: Image should still have a ratio Reproducible: Always User Profile Reset: No Additional Info: Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 37e3455a13ab5741104bf41d05a80e60a4612682 CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: nl-NL (nl_NL); UI: en-US Calc: CL threaded
1. Open attachment 185930 [details] 2. Select the image and press F4 3. Position and size Tab 4. Check the Keep Ratio checkbox 5. Width: Check the Relative to checkbox 6. Uncheck the Relative to checkbox -> FINE 7. Recheck the Relative to checkbox -> FINE 8. Apply by Press OK 9. F4 10. Uncheck Relative to checkbox -> Height changes into 17 (same as Width)
Different route: same result: 1. Open attachment 185930 [details] 2. Select the image and press F4 3. Position and size Tab 4. Check the Keep Ratio checkbox 5. Width: Check the Relative to checkbox 6. Press OK 7. Press F4 again -> everything unchanged (OK) 8. Check Keep Ratio (nothing changes -> Fine 9. Press OK 10. F4 11. Uncheck Keep Ratio -> 17 CM appears Expected: keep ratio should make a difference; result should be the same as in steps 1-7
Repro with comment 1 steps in: Version: 7.6.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: b5a22fceed57f05eb43a5fb0817afbc141610c5e CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded Same in: Version: 6.0.0.3 Build ID: 64a0f66915f38c6217de274f0aa8e15618924765 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk2; Locale: en-AU (en_AU.UTF-8); Calc: group and in OOo 3.3, so inherited.
Already tracked in bug 55480. *** This bug has been marked as a duplicate of bug 55480 ***