Bug 142313

Summary: Bad import of OOXML documents related to tdf#136841 on macOS
Product: LibreOffice Reporter: Thorsten Wagner <thorsten.wagner.4>
Component: UIAssignee: Thorsten Wagner <thorsten.wagner.4>
Status: RESOLVED DUPLICATE    
Severity: normal CC: gang65, lo, sberg.fun
Priority: medium    
Version: 7.1.0.0.alpha0+   
Hardware: All   
OS: macOS (All)   
Whiteboard:
Crash report or crash signature: Regression By:
Attachments: Sample document
EMF file extracted from the docx

Description Thorsten Wagner 2021-05-16 12:28:29 UTC 
Description:
Since support of retina graphics on macOS OOXML documents related to tdf#136841 are no longer imported correctly (see comments on https://gerrit.libreoffice.org/c/core/+/109072).

Steps to Reproduce:
1. Start LO with retina display active
2. Open sample OOXML document sw/qa/extras/ooxmlexport/data/tdf136841.docx

Actual Results:
Green square without document page background

Expected Results:
Document with single red left arrow


Reproducible: Always


User Profile Reset: No



Additional Info:
Issue exists if one retina display is active at least. Without retina displays (e.g. laptop external non-retina display and lid closed) issue do not exist. Cause is retina graphics support which becomes active if one retina display is active at least (e.g. laptop with lid open).
Comment 1 Thorsten Wagner 2021-05-16 12:29:00 UTC 
Created attachment 172057 [details]
Sample document
Comment 2 Valek Filippov 2021-05-16 13:05:47 UTC 
Created attachment 172059 [details]
EMF file extracted from the docx

The file imitates gradient fill by drawing 160 polygons with slightly changed coordinates and color. There are also few EMF+ records (no drawing, only set states).
Comment 3 Thorsten Wagner 2021-05-19 13:02:30 UTC 
Issue seems to be caused by missing scaling operations for XOR emulation. These will be added in scope of tdf#142061. Patch is under preparation.

I will mark this ticket as duplicate of tdf#142061. Further work takes there.
Comment 4 Thorsten Wagner 2021-05-19 13:03:04 UTC 

*** This bug has been marked as a duplicate of bug 142061 ***