Bug 154704 - Wrong section of frame area covered by paragraph background colour
Summary: Wrong section of frame area covered by paragraph background colour
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
5.3 all versions
Hardware: All All
: medium minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: bibisected, bisected, filter:docx
Depends on:
Blocks: DOCX-Frames
  Show dependency treegraph
 
Reported: 2023-04-07 20:31 UTC by Justin L
Modified: 2025-04-12 03:12 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
n592908-frameC_word2010.pdf: how it looks in MS Word (25.39 KB, application/pdf)
2023-04-07 20:31 UTC, Justin L
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Justin L 2023-04-07 20:31:54 UTC
Created attachment 186535 [details]
n592908-frameC_word2010.pdf: how it looks in MS Word

In attachment 186534 [details] (From bug 154703) we have a frame with 3 paragraphs. The first two paragraphs have a different background colour specified, and the third is empty.

The problem is that the second (empty) paragraph's blue band is covering a couple of lines of text from paragraph one. This is because the paragraph has a top border spacing defined, and that is applying even though the properties "merge with the next paragraph".

It became visible with LO 5.3 commit 9130627e21dd7c52c5eee1acc4b71f86eb9f3118
Author: Justin Luth on Mon Oct 31 11:59:09 2016 +0300
    tdf#41542 globally allow padding without borders: layout

I don't think I'd call this a regression - I think it exposed an existing failure to absorb the merged spacing. Prior to this there was a "white gap" between the paragraphs - it is good that this gap at least is gone.

I was not able to replicate this in a clean document though... reducing severity.
Comment 1 Buovjaga 2023-04-12 13:50:38 UTC
Confirmed.

I opened the docx in office.com and it was rendered similarly, also having padding inside the box, so the background colours did not touch the sides. Saving it as PDF was almost like your MSO 2010 PDF, except the colours were bleeding out from the left side. So MSO has also evolved.

Arch Linux 64-bit, X11
Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: b8cc40c906d4838b028e332e9dabbacba7f7c033
CPU threads: 8; OS: Linux 6.2; UI render: default; VCL: kf5 (cairo+xcb)
Locale: fi-FI (fi_FI.UTF-8); UI: en-US
Calc: threaded
Built on 12 April 2023
Comment 2 QA Administrators 2025-04-12 03:12:27 UTC
Dear Justin L,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug