Created attachment 134210 [details] Sample XLSX In the attached spreadsheet a rectangle covers most of the numbers, but is set to invisible, so it's not shown. It's not shown in Print Preview and when exported to PDF, either. So far so good. However, it is shown in Print dialog's preview, and also appears during printing, which is bad. I wanted to check the same with native formats, but I don't see the possibility to show/hide drawing objects in LibreOffice, the transparency of line/fill can be adjusted separately, and that displays fine in Print dialog as well. Observed using LO 5.4beta2 & 4.0.0.3 / Windows 7.
The difference between the two drawing object XMLs is the extra "hidden" attribute: <xdr:cNvPr id="2" name="Rectangle 1" hidden="1"/>
Bug is already in 3.3.0.
Confirmed in Version: 6.0.0.0.alpha0+ Build ID: 08f6f9dded1b142b858c455da03319abac691655 CPU Threads: 4; OS Version: Linux 4.8; UI Render: default; VCL: gtk3; Locale: ca-ES (ca_ES.UTF-8); Calc: group
The situation is more complicated, there are two related elements in OOXML that affect whether the drawing object is there or not: - attribute "hidden" of element "cNvPr" [1] that controls whether the drawing object is displayed, - attribute "fPrintsWithSheet" of element "clientData" [2] that controls whether the drawing object is printed. A hidden drawing object is not printed (at least not shown in the preview), but there's no mention of that in the specification. The relevant properties for binary formats can be found in MS-ODRAW, under 2.3.4.44 Group Shape Boolean Properties (fUsefHidden, fUsefPrint, fHidden, fPrint). In LibreOffice, as noted in [3], <drawooo:display> holds this setting, which is not part of the standard, but is similar to ODF's <draw:display> [4] for layers. As far as I could see there's no option on the UI where it can be set for shapes. Relevant pieces of the import code: - OOXML: shape is created here based on the imported data http://opengrok.libreoffice.org/xref/core/oox/source/drawingml/shape.cxx#615 - OOXML: client data is imported here http://opengrok.libreoffice.org/xref/core/sc/source/filter/oox/drawingbase.cxx#118 - binary format: similar properties are read and passed further http://opengrok.libreoffice.org/xref/core/sc/source/filter/excel/xiescher.cxx#3527 In OOXML's case the question is, where should the two attributes with different origins be processed together? [1] https://msdn.microsoft.com/en-us/library/documentformat.openxml.drawing.spreadsheet.nonvisualdrawingproperties(v=office.15).aspx [2] https://msdn.microsoft.com/en-us/library/documentformat.openxml.drawing.spreadsheet.clientdata.aspx [3] https://issues.oasis-open.org/browse/OFFICE-2125 [4] http://docs.oasis-open.org/office/v1.2/os/OpenDocument-v1.2-os-part1.html#attribute-draw_display
Created attachment 134369 [details] Samples with combinations of hidden/not printed settings The conceptual difference is actually an issue. Office saves all four combination of hidden / fPrintsWithSheet settings in the file, since the two settings can be turned off/on independently. However, if the shape is hidden, the sheet displays and prints the same regardless of the other setting. Therefore in LO not only both have to be translated to the same ODF setting ("none"), afterwards it can't be unambiguously converted back to Excel format. In that case "none" should probably be converted back to hidden and printing as the more likely combination (and hidden and not printing would get lost).
** 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 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 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: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Still exists in 6.1.0.3.
Aron Budea committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=b38065ea941375bf4f78f13314e84f4a875545d9 tdf#108691, tdf#119639 Don't print hidden objects in XLS(X) It will be available in 6.2.0. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
The case in the description should now be fixed, for a related issue I've opened bug 119764.
*** Bug 116028 has been marked as a duplicate of this bug. ***