We need our business documents to have a background image, that goes beyond the textarea. Due to the lack of an option to stretch the background image to the whole page (not only the writable textarea) we are forced to set our page margins to 0,00 and emulate this missing spaces by applying a border with spacing to each page. (see screenshots how this is done) Under these circumstances the following misbehaviour in calculating tabstopp positions reveals. Assume we need a (optical) page margin of 2.00 cm. Then we would set the page margins to 0.00 cm and the border spacing would be set to 2.00 cm. If now a text is written and a tabstopp is set by clicking the horizontal ruler at 5.00 cm the text will start at 7.00 cm. (see example document) Writer seems to calculate the position of the tabstopp by adding the border spacing to the page margin. As a result the tabstop is placed at 7cm instead of 5cm. The expected behaviour is that tabstopps positions are *always* only calculated from the beginning of the page margin - no matter what border spacing is used. This also better confirms to the users expectation when clicking the horizontal ruler (or defining a tabstopp in format dialog). P.S. It would also be nice if an option was introduced, that allows a background image to be stretched to the *whole* page.
Created attachment 97407 [details] An example document.
Created attachment 97408 [details] The settings used for page margins.
Created attachment 97409 [details] The settings used for border spacing.
Created attachment 97734 [details] Document created with 4.3 Hi, I could reprocuce the bug
I am very sorry for this noise, but this is expected behaviour (if you think about it): Borders are, in the same way as the page margains drawn at the real (natural) borders of the page. A tabulator with 5cm is content right? Add 2 cm for the "Space to the content" from the border and you got the 7cm. So, it is desired behaviour....
> I am very sorry for this noise, but this is expected behaviour (if you think > about it): Borders are, in the same way as the page margains drawn at the > real (natural) borders of the page. A tabulator with 5cm is content right? > Add 2 cm for the "Space to the content" from the border and you got the 7cm. > So, it is desired behaviour.... If you only think about it theoretically and light-minded you seem to be right, that the spacing should be added to the page margins. But if you think about it once more, you will see that the current behaviour ob setting tabstopps (by clicking the ruler) produces unexpected results. It should never be "desired behaviour" to produce unexpected results (even if technically everything seems to be right). You can turn it as you want: Either the calculation of the spacing is correct, then setting the tabstopps is erroneous. Or you might argue that creating the tabstopps ist correct, then the calculation of the spacing must be erroneous. Currently the calculation of the spacing and the function to set the tabstopps do *NOT* fit together. I feel that the first case applies and the function to set tabstopps is wrong 'cause it does not expect that a border spacing > 0 can exist.
I think this is a bug, yes - or at least something to inspect in the code.
** 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 (4.4.3 or later) 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 your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-06-08
Tested with LO 5.1.5.2 (x64) on Windows Server 2k8 R2 x64: The problem still exists in the same way as written above.
also tested with LO 5.1.5.2 (x64) on Windows 7: The problem still exists in the same way as written above.
** 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
retestet with Version: 5.2.7.2 (x64) Build-ID: 2b7f1e640c46ceb28adf43ee075a6e8b8439ed10 CPU-Threads: 10; BS-Version: Windows 6.1; UI-Render: Standard; Gebietsschema: de-DE (de_DE); Calc: group => problem still exists
retestet with: Version: 6.1.3.2 Build-ID: 1:6.1.3-2 CPU-Threads: 2; BS: Linux 4.18; UI-Render: Standard; VCL: x11; Gebietsschema: de-DE (de_DE.UTF-8); Calc: group threaded and Version: 6.0.6.2 (x64) Build-ID: 0c292870b25a325b5ed35f6b45599d2ea4458e77 CPU-Threads: 16; BS: Windows 6.1; UI-Render: Standard; Gebietsschema: de-DE (de_DE); Calc: group => problem still exists in both cases
Dear a07cd040897db54e103c, 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://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
Dear a07cd040897db54e103c, 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
retested with: Version: 7.0.4.2 Build ID: 00(Build:2) CPU threads: 16; OS: Linux 5.10; UI render: default; VCL: gtk3 Locale: de-DE (de_DE.UTF-8); UI: de-DE Debian package version: 1:7.0.4-4+deb11u4 Calc: threaded => problem still exists
retested with: Version: 7.4.5.1 / LibreOffice Community Build ID: 40(Build:1) CPU threads: 8; OS: Linux 6.1; UI render: default; VCL: gtk3 Locale: de-DE (de_DE.UTF-8); UI: de-DE Debian package version: 4:7.4.5-2 Calc: threaded => problem is FIXED Thank you!