Bug 148608 - Slide has background with 'hairlines' in powerpoint but not in LibO (and get lost on round trip)
Summary: Slide has background with 'hairlines' in powerpoint but not in LibO (and get ...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
Version:
(earliest affected)
3.5.0 release
Hardware: All All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-04-15 07:27 UTC by Telesto
Modified: 2022-04-15 22:22 UTC (History)
2 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 Telesto 2022-04-15 07:27:31 UTC
Description:
Slide has background with 'hairlines' in Powerpoint but not in LibO

Steps to Reproduce:
1. Open attachment 129074 [details] (bug 104222) with PowerPoint and with LibreOffice
2. White background in Impress

Actual Results:
White background

Expected Results:
Hairlines


Reproducible: Always


User Profile Reset: No



Additional Info:
Version: 7.4.0.0.alpha0+ (x64) / LibreOffice Community
Build ID: efe854bf9b6daff3d0ecf6e3d04bd9a50bfaa3f3
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 Jumbo

and in
4.4.7.2

and in
3.5.0
Comment 1 Regina Henschel 2022-04-15 22:13:34 UTC
That is the special fill "Slide background fill" of an object. The object is not transparent but copies the underlying slide background. So it looks as if the object makes a hole in the shapes between itself and the slide background. It depends on the position of the shape, which part of the background of the slide is shown.

It can neither be solved by setting the shape background the same as the slide background nor by setting the shape background transparent.

LibreOffice is not able to render this special fill and it cannot be expressed in current ODF. It is the attribute "useBgFill" in OOXML.

I'm quite sure there are already reports about this problem. It might be bug 128150 or bug 147852. It is a missing OOXML feature, so set to enhancement.