This is an oldish bug (from the LO project start, maybe older) but I did not found it filed. How to reproduce: format a paragraph with indent before text (left side), add two or more tab stops (remember tab stops position values). For example – Indent befor text: 1 cm; Tabs positions: 3 cm, 5 cm. (Re)open menu Format>Paragraph>Tabs and alter desired tab position (say 3 cm) options (Type, Fill). Hit OK. UNexpected result: Indent befor text: 1 cm; Tabs positions: 4 cm, 5 cm. Lets set indent before text to 2 cm. Result (expected): Indent befor text: 2 cm; Tabs positions: 5 cm, 6 cm. Then alter options of the second tab position (5 cm). UNexpected result: Indent befor text: 2 cm; Tabs positions: 5 cm, 8 cm. Conclusion: the value of indent is allways added to edited tab position, when there are two or more tabs stops.
Hello Antanas, Thank you for submitting the bug. I can confirm that the bug is available in 4.2.7, 4.3.2, and master. Steps: 1) Open Writer 2) right-click > Paragraph 3) in indents tab, set indent before text to 1cm 4) in tabs tab, add a tab position at 3cm 5) press OK 6) tab position will be set to 4cm
Hello Jay, (In reply to comment #1) > Hello Antanas, > > Thank you for submitting the bug. I can confirm that the bug is available in > 4.2.7, 4.3.2, and master. > > Steps: > 1) Open Writer > 2) right-click > Paragraph > 3) in indents tab, set indent before text to 1cm > 4) in tabs tab, add a tab position at 3cm > 5) press OK > 6) tab position will be set to 4cm You are describing a different case and *may*be* an intended behavoir (there is still 3 cm between paragraph's left side and tab-stop). At least, the 4 cm tab position remains intact after returning editing of tab properties. In my original bug description (using two or more tab-stops) tab position moves further *each*time* you are editing tab properties. Therefore I'm not fully agree with your version of the bug summary.
(In reply to comment #2) > Hello Jay, Hi Antanas, > You are describing a different case and *may*be* an intended behavoir (there > is still 3 cm between paragraph's left side and tab-stop). At least, the 4 > cm tab position remains intact after returning editing of tab properties. I dont think this should be the intended behaviour as the values set in the tab page should be absolute values and not dependent on the indent value. > In my original bug description (using two or more tab-stops) tab position > moves further *each*time* you are editing tab properties. > Therefore I'm not fully agree with your version of the bug summary. I can still reproduce your bug with doing it for one tab stop.
(In reply to comment #3) > (In reply to comment #2) > > Hello Jay, > > Hi Antanas, > > > You are describing a different case and *may*be* an intended behavoir (there > > is still 3 cm between paragraph's left side and tab-stop). At least, the 4 > > cm tab position remains intact after returning editing of tab properties. > > I dont think this should be the intended behaviour as the values set in the > tab page should be absolute values and not dependent on the indent value. > > > In my original bug description (using two or more tab-stops) tab position > > moves further *each*time* you are editing tab properties. > > Therefore I'm not fully agree with your version of the bug summary. > > I can still reproduce your bug with doing it for one tab stop. Not exactly. If you extend your bug reproduction – open paragraph formatting once again and set e. g. tab fill character to "dot" – the tab position remains as it was before. Is it true? By having two or more tab positions, the last (right-most) tab position each time increments by value of left indent. P.S. I just noticed that if I set paragraph's left indent to arbitrary non-zero value and add two or more tab positions – all in one take, by pressing <OK> one tab position is lost.
(In reply to comment #4) > Not exactly. If you extend your bug reproduction – open paragraph formatting > once again and set e. g. tab fill character to "dot" – the tab position > remains as it was before. Is it true? > By having two or more tab positions, the last (right-most) tab position each > time increments by value of left indent. When you open up the dialog again, you have to first select the entry in the position list and then change its properties, or else it is thinking that your modifying the options of a new entry you are going to add. > P.S. I just noticed that if I set paragraph's left indent to arbitrary > non-zero value and add two or more tab positions – all in one take, by > pressing <OK> one tab position is lost. I had noticed that as well after working on your bug and filed a bug for it (bug 82436). :D
** 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.0.0.5 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-09-03
The bug is still reproducible in LibreOffice 5.0.1.2 00m0(Build:2) using Ubuntu 14.04 LTS 32 bit
** 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
The original bug is still present in LibreOffice 5.2.1.2 20m0(Build:2) Ubuntu 14.04.5 LTS and Ubuntu 16.04.1 LTS
** 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
Dear Antanas, 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 Antanas, 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
*** Bug 154925 has been marked as a duplicate of this bug. ***
Still present in Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 006b35d50024b1932d84380b5d2fec1f7066bccd CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: en-US (de_DE); UI: en-GB Calc: CL threaded
The fact whether the tab position is relative to the indent is determined by the setting TabsRelativeToIndent in the subdocument settings.xml. For documents originally created in LibreOffice its default value is "true", for documents imported from docx the value is "false". There is currently no UI for this setting. You need a macro or edit the markup in the file source to change it. In ODF 1.4 this setting will belong to the paragraph style.
Created attachment 189364 [details] test ODT (In reply to Regina Henschel from comment #15) > The fact whether the tab position is relative to the indent is determined by > the setting TabsRelativeToIndent in the subdocument settings.xml. For > documents originally created in LibreOffice its default value is "true", for > documents imported from docx the value is "false". There is currently no UI > for this setting. You need a macro or edit the markup in the file source to > change it. > > In ODF 1.4 this setting will belong to the paragraph style. The tab position being relative to the indent is fine, and having UI to change that is welcome, but the bug here is that the indent value is added to the tab stop position for all but the first custom tab stop when it's edited - even when the position isn't touched. See for example with the attachment: Steps to reproduce: 1. Open attachment, created in LibreOffice, which has: - indent at 1 cm - 3 tab stops at 2, 4 and 6 cm. 2. In Format > Paragraph > Tabs, change the tap Type of all three tabs to any other, e.g. "Right". Click OK. Result A: First tab stop does not move; second and third tab stops get 1 extra cm in their position. 3. In Format > Paragraph > Tabs, change type back to "Left" for all three. Click OK. Result B: all three tabs get an extra 1 cm in position. What needs to be fixed: - Inconsistency in how the first tab behaves compared to others - If tab position is relative according to document setting, make it transparent (with a hint in the dialog telling the user what the value is exactly) and do not add the indent size _every single time_ the tabs are modified. Tested in: Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: cc7d6211bc01e5ec84dbad542605d2e93dea925c CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded
(In reply to Stéphane Guillou (stragu) from comment #16) > 3. In Format > Paragraph > Tabs, change type back to "Left" for all three. > Click OK. > Result B: all three tabs get an extra 1 cm in position. Checking once more, Result B is again like Result A, so you can ignore that. Fact is: indent value keeps being added at each tab modification even if the position value isn't touched.
Hi testers, we are in the tenth year after the bug submission by me and still no resolution. Thank you Stéphane for the detalisation. The bug persists. Version: 7.4.7.2 / LibreOffice Community Build ID: 40(Build:2) CPU threads: 4; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: lt-LT (lt_LT.UTF-8); UI: lt-LT Ubuntu package version: 1:7.4.7~rc2-0ubuntu0.20.04.1~lo1 Calc: threaded
*** Bug 152240 has been marked as a duplicate of this bug. ***