When printing a sheet that has cells formatted with the property to "hide with printing", the cell contents and borders are not printed, but the background color is printed. I believe this is incorrect behavior. This is true regardless of the setting of the "tools\options\calc\print\suppress output of empty pages" item. I believe the background color of a cell should be a property of the cell and it should be printed or not printed when the cell is printed or not printed. The cell may be printed or not, but it is not correct to print some parts of the cell and not others. I believe the CELL should have properties of: content (text, for example) background color border etc. If a CELL is protected from printing with "hide when printing", no property of that cell should be printed - including the background color. If a CELL has background color but no text content and no border, then the cell is not null and it should be printed unless the "hide when printing" property is set. If all of the cells on a printable page have no content, no background color and no border, or were marked as "hide when printing" then that page would be elgible to be print-suppressed depending up the "suppress output of empty pages" setting. I believe thinking about cell(s) this way would clear up all of these inconsistencies when printing.
reproduced in 3.3.4 and 3.5.2 on Fedora 64 bit and Winows 7 32 bit changing version to 3.3.4 as most early reproducible
reproducible with LO 4.3.1.2 (Win 8.1)
reproducible with LO 4.3.5 / Win7-64. If no printing range is defined, pages that contain only cells with hidden content will generated and printed. The print shows borders and/or background colors. Also if the sheet contains on the "first page" only hidden cells without borders and/or background colors an empty page will be shown and printed. After 'protect cell' + 'hide all' + 'protect sheet' the "empty" cells and their formats remain visible on the screen. Is this the intended behaviour because only a whole column/row can be hidden?
*** Bug 91644 has been marked as a duplicate of this bug. ***
** Please read this message in its entirety before responding ** 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 on a currently supported version of LibreOffice (5.1.5 or 5.2.1 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) http://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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20160920
This bug still exists in version 5.2.1 Fresh. Behavior has changed slightly, either in v 4.x.x or 5.x.x, so that now if a cell has text contents, a border, and a background color, and is formatted to 'hide when printing', the text is not printed (as expected) but the border is printed and the background color is printed. When first observed, some many version back, borders and text contents were suppressed, but only the background color was printed.
Not sure if this a bug or not, as i wouldnt classify the cell background to be part of the cell data unless maybe it was formatted based on conditional formatting, but lets see what the exports say. @Regina: What does ODF say about this setting? https://help.libreoffice.org/Calc/Cell_Protection
(In reply to Yousuf Philips (jay) from comment #8) > Not sure if this a bug or not, as i wouldnt classify the cell background to > be part of the cell data unless maybe it was formatted based on conditional > formatting, but lets see what the exports say. @Regina: What does ODF say > about this setting? > > https://help.libreoffice.org/Calc/Cell_Protection Yes, it's a bug. The setting is to hide or display the entire CELL, not just the text. The cell's color, border and text contents are all part of and properties of the cell. Otherwise you can have a sheet that's full of "hidden when printing" cells, blank, but instead of a printed blank sheet you get a sheet with a bunch of scattered yellow rectangles with no text.
The attribute is in ODF 20.323.3. The only description there is, "The style:print-content attribute specifies if cell content is printed." But the background of the cell is an attribute of the cell and not a content. Therefore I think, that it is correct, that the background is printed. I see no way in the file format to exclude the background from printing.
(In reply to Phil Nichols from comment #9) > Yes, it's a bug. The setting is to hide or display the entire CELL, not just > the text. As Regina has confirmed that the file format setting is to hide only the cell content, i'm closing this bug accordingly.
*** Bug 152372 has been marked as a duplicate of this bug. ***