Created attachment 120792 [details] Example produced with LO 5.1 How to produce an example document: Start with an Impress or Draw document. Insert an image. Switch to text edit mode (press F2) and enter some text. Open Format > Text and set the 'text anchor' to center/bottom and the 'Spacing to Borders' part 'Bottom' to -2cm. Save the document. The entered text will be below the image, so it can be used as description of the image. This allows to attach text to a drawing object without grouping. Unpack the document and open the file content.xml. You will find an element style:style with style:family="graphic" and child <style:graphic-properties>. Therein you will find the attributes "draw:textarea-vertical-align="bottom" and "fo:padding="-2cm". Now look into the specification part 1, section "20.211 fo:padding-bottom". It specifies, "The fo:padding-bottom attribute has the data type nonNegativeLength 18.3.20." And you find the same restriction, when you follow the link to [XSL]. There you can read, "Unlike margin properties, values for padding properties cannot be negative." OpenOffice.org has written negative values since the beginning, although in ODF 1.1 it is already of attribute type "nonNegativeLength".
Reproduced in LO 5.2.0.4.
** 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.4.1 or 5.3.6 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-20170901
The problem is still unsolved in Version: 6.0.0.0.alpha0+ Build ID: 4c99b8a9de59f3c5280ff2944d9f828822897f4a CPU threads: 4; OS: Windows 6.1; UI render: default; Locale: de-DE (de_DE); Calc: group A valid solution is to use a fo:clip attribute with a negative offset. That would result in a different bounding box, but is as good workaround.
** 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
The error still exists in Version: 6.2.0.0.alpha0+ (x64) Build ID: 414ef6cb187dd3bbcc917dbedf3c0c1cc8668f60 CPU threads: 8; OS: Windows 10.0; UI render: GL; TinderBox: Win-x86_64@42, Branch:master, Time: 2018-08-21_00:13:04 Locale: de-DE (en_US); Calc: CL
Dear Regina Henschel, 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
bug still present in LO 7.0
We might want to consider to fix this in the export filter of ODF 1.2 and ODF 1.3, still not remove it but extend the standard of ODF 1.4 to allow negative padding. By this we would become more interoperable with CSS, which does allow negative values (length) in width, margin, padding, font-size, border-width und text-shadow. I have not looked up OOXML, but it would be interesting to take their behavior into account as well.
(In reply to Svante Schubert from comment #8) > By this we would become more interoperable with CSS, which does allow > negative values (length) in width, margin, padding, font-size, border-width > und text-shadow. Negative padding is not allowed in CSS 2.1. "Unlike margin properties, values for padding values cannot be negative." in section 8.4 in https://www.w3.org/TR/CSS21/box.html Negative padding is not allowed in upcoming CSS 3. "Negative values for padding properties are invalid." in section 4.1 in https://drafts.csswg.org/css-box-3
Oh, thank you Regina. I was instantely clicking on the <length> link and have not read the paragraph(s) after the list: https://www.w3.org/TR/CSS22/box.html#value-def-padding-width
(In reply to Svante Schubert from comment #8) > I have not looked up OOXML, but it would be interesting to take their > behavior into account as well. The corresponding property in OOXML is the attribute "space" of borders. You find it in "17.3.4 Border Properties". Its value is specified as ST_PointMeasure simple type, 17.18.68. And there you find "This simple type's contents are a restriction of the ST_UnsignedDecimalNumber datatype". And Microsoft restricts is further in its 'Office Implementation Information for ISO/IEC 29500 Standards Support': "Word restricts the contents of this simple type to be at least 0 and at most 31." So OOXML does not use negative values for padding.
I suggest to restrict the UI, so that input of negative padding is no longer possible. @Heiko, wouldn't that be something for you? A different problem is, how to handle documents, which have already a negative padding. Any idea? We cannot silently set a negative padding to zero when resaving the document, because that will unexpectedly change the layout.
(In reply to Regina Henschel from comment #12) > I suggest to restrict the UI, so that input of negative padding is no longer > possible. Setting the minimum value on the GtkAdjustments in cui/uiconfig/ui/textattrtabpage.ui instantiated in cui/source/tabpages/textattr.cxx does this. Loading your document still shows the text with -2cm but I cannot change it, meaning the dialog shows 0cm and either okaying this or some other positive value keeps the distance. With some visual glitches I expect the app to crash. Running the test in a new document seems to work flawless.
Dear Regina Henschel, 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
The error still exists in Version: 24.2.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: 43967453e15e1d054972a7586cfef8f8e0866270 CPU threads: 32; OS: Windows 10.0 Build 22631; UI render: Skia/Vulkan; VCL: win Locale: de-DE (de_DE); UI: en-US Calc: threaded