Bug 139080 - Wrong ratio, when changing anchor of a rotated image ratio to 'as character'
Summary: Wrong ratio, when changing anchor of a rotated image ratio to 'as character'
Status: RESOLVED DUPLICATE of bug 125594
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:
Depends on:
Blocks: Anchor-and-Text-Wrap
  Show dependency tree / graph
 
Reported: 2020-12-19 20:36 UTC by Telesto
Modified: 2021-01-03 16:37 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Attachments
Example file (663.75 KB, application/vnd.oasis.opendocument.text)
2020-12-19 20:36 UTC, Telesto 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Telesto 2020-12-19 20:36:24 UTC 
Description:
Image crop results in strange ratio when anchoring as character in table cell

Steps to Reproduce:
1. Open the attached file
2. Select the image 
3. right click -> Change anchor to 'as character'

Actual Results:
Crop frame & image mismatches. Likely missed when fixing the wrong orientation of the crop 

Expected Results:
Should be the same


Reproducible: Always


User Profile Reset: No



Additional Info:
Found in
7.2

6.2

Versie: 6.0.4.1
Build ID: a63363f6506b8bdc5222481ce79ef33b2d13c741
CPU-threads: 4; Besturingssysteem: Windows 6.3; UI-render: GL; 
Locale: nl-NL (nl_NL); Calc: CL

Crop was wrong in 5.3
Comment 1 Telesto 2020-12-19 20:36:43 UTC 
Created attachment 168347 [details]
Example file
Comment 2 Dieter 2021-01-03 16:35:16 UTC 
I confirm it with

Version: 7.2.0.0.alpha0+ (x64)
Build ID: c0eee433e079d8e3413f4691607e075b99af92b0
CPU threads: 4; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win
Locale: de-DE (de_DE); UI: en-GB
Calc: threaded

The bug occurs, since the image is rotated with 270°. If you change rotation to 0° it works as expected.

=> I would treat it as duplicate of bug 125594

*** This bug has been marked as a duplicate of bug 125594 ***
Comment 3 Dieter 2021-01-03 16:37:58 UTC 
Additional information: Duplicate, because bug occurs also outside a table.