Bug 144847 - Changing anything on the Type tab of Image Properties box causes image to become square
Summary: Changing anything on the Type tab of Image Properties box causes image to bec...
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.2.0.4 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-10-01 01:52 UTC by ravenkwill
Modified: 2022-05-03 11:09 UTC (History)
1 user (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 ravenkwill 2021-10-01 01:52:44 UTC
Description:
For the last week, the image property tab has been malfunctioning. When the Keep ratio field is checked. clicking on the width or height fields causes that field value to change to match the other field (always forming a square image).

When this happens, clicking the Original Size button allows me to change one of the fields and the other responds as expected.

Also, if I then save the image properties, close the properties box and go back in, making any changes to the position then causes the image to flip back to square.

Steps to Reproduce:
1.Open an image properties box
2.Check Keep ratio
3. Save and close image property box
4. Re-open image property box 
5.Click in either Width or Height

Actual Results:
Image field setting immediately changes to match the other measurement (ie click in Width, the width changes to be the same as the height). Changing the number in the field causes the other field to change to exactly match the number just entered.

Expected Results:
No change on clicking in the field box. Changing the field number causes other field to change in ratio.


Reproducible: Always


User Profile Reset: Yes


OpenGL enabled: Yes

Additional Info:
Problem persists in safe mode
Comment 1 Telesto 2021-10-01 13:40:49 UTC
Is this still present in 7.2.1.. A bug in this area has been fixed
Comment 2 ravenkwill 2021-10-04 22:09:21 UTC
This works properly with 7.2.1
Comment 3 Xisco Faulí 2022-05-03 11:09:26 UTC
Setting to RESOLVED WORKSFORME since the commit fixing this issue hasn't been
identified.