Bug 130607 - PDF Export (Calc): Cell background can spill into margin when merged cells overlap multiple pages
Summary: PDF Export (Calc): Cell background can spill into margin when merged cells ov...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Printing and PDF export (show other bugs)
Version:
(earliest affected)
5.0.0.5 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: bibisected, bisected, regression
Depends on:
Blocks: PDF-Export
  Show dependency treegraph
 
Reported: 2020-02-12 02:52 UTC by Aron Budea
Modified: 2023-04-10 13:55 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Sample ODS (7.38 KB, application/vnd.oasis.opendocument.spreadsheet)
2020-02-12 02:52 UTC, Aron Budea
Details
Exported PDF with incorrect background (9.41 KB, application/pdf)
2020-02-12 02:53 UTC, Aron Budea
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Aron Budea 2020-02-12 02:52:01 UTC
Created attachment 157810 [details]
Sample ODS

- Open attached ODS, which has a merged cell overlapping to the next page, with background color set.
- Export to PDF.

=> In the PDF, the background color extends over the margin, it should end where the text is cut off.

Observed using LO 7.0.0.0.alpha0+ (d41d7ecb60fb38204fafcb1aa4595992721855e6), 5.0.0.5 / Ubuntu.
Exported PDF is fine in 4.4.0.3.
=> regression

Bibisected to the following commit using repo bibisect-50max. Adding CC: to Markus Mohrhard.

https://cgit.freedesktop.org/libreoffice/core/commit/?id=09a67a5bcec037fd837bb515c6c00a12e68e2ea5
author		Markus Mohrhard <markus.mohrhard@googlemail.com>	2015-05-18 19:54:20 +0200
committer	Markus Mohrhard <markus.mohrhard@googlemail.com>	2015-05-18 19:58:01 +0200

render vertically merged cells together
Comment 1 Aron Budea 2020-02-12 02:53:38 UTC
Created attachment 157811 [details]
Exported PDF with incorrect background
Comment 2 QA Administrators 2022-02-12 03:37:29 UTC
Dear Aron Budea,

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