Description: Converting tabbed text to bullets loses the tab in the last line Steps to Reproduce: 1. create 3 lines of "<tab>hello" 2. highlight the three lines (excluding the EOL of the third line) 3. click on the bullet button Actual Results: Last bulleted line loses the preceding tab Expected Results: Last line should preserve the preceding tab Reproducible: Always User Profile Reset: No Additional Info: Selecting the EOL in the last line (or ctrl-a) and then bulleting preserves the tab. Seen in: Version: 5.2.7.2 Build ID: 1:5.2.7-1 CPU Threads: 2; OS Version: Linux 4.9; Version: 5.4.0.2 (x64) Build-ID: 2b906d450a44f2bbe506dcd22c51b3fa11dc65fd CPU-Threads: 4; Betriebssystem:Windows 6.1 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0
Also (not sure if this is part of the same bug, or a separate one): - create a line with <tab><tab>hello - bullet it (tab gets eaten) - unbullet it (text is left-margin aligned) - re-bullet it (bullet is in a different position, close to the left margin) Doing the same thing with only one leading tab also shows the alignment difference (but not the tab being eaten)
Created attachment 135550 [details] Screenshot It does not lose the tab, but creates extra tabs for bullets depending on the direction of the selection. Arch Linux 64-bit, KDE Plasma 5 Version: 6.0.0.0.alpha0+ Build ID: a7ed6a9731f0101fe1454638135bb30f5dcb4f88 CPU threads: 8; OS: Linux 4.12; UI render: default; VCL: kde4; Locale: fi-FI (fi_FI.UTF-8); Calc: group Built on August 14th 2017
Created attachment 135551 [details] Example file to play with
Already in 3.3 Arch Linux 64-bit LibreOffice 3.3.0 OOO330m19 (Build:6) tag libreoffice-3.3.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 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
Confirmed still present in Version: 6.0.3.2 Build ID: 1:6.0.3-0ubuntu1 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: kde4; Locale: en-US (en_US.UTF-8); Calc: group
Dear internationils, 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 present Version: 6.2.7.1 Build ID: 1:6.2.7-0ubuntu0.19.04.1 CPU threads: 8; OS: Linux 5.0; UI render: default; VCL: kde5; Locale: en-US (en_US.UTF-8); UI-Language: en-US Calc: threaded
Still present in Version: 6.4.3.2 Build ID: 1:6.4.3-0ubuntu0.20.04.1 CPU threads: 8; OS: Linux 5.4; UI render: default; VCL: kf5; Locale: en-US (en_US.UTF-8); UI-Language: en-US Calc: threaded
repro 7.2+
This is from sw/source/uibase/wrtsh/wrtsh1.cxx's SwWrtShell::NumOrBulletOn calling RemoveLeadingWhiteSpace(). author Kurt Zenkeron 2005-01-21 09:44:26 +0000 with commit c84f75834b94a98380494fc0855cd8cc0df235a1 changed RemoveLeadingChars to RemoveLeadingWhiteSpace. This was a slight change to author Rüdiger Timm on 2004-10-22 07:15:19 +0000 commit 651e60f73a677844de3f87055c07093a1d59ea5a #i30314# convert tabs to numindent So the OOo bug deliberately removed all leading whitespace, and this bug report seems to expect the same thing (wondering why tabs were "added"). So the most reasonable fix seems to be that each paragraph in the selection should RemoveLeadingWhiteSpace.
Justin Luth committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/3e3328987b69a2a549d24c79ee71b353b9a3e288 tdf#109285 sw numbering: RemoveLeadingWhiteSpace from all paras It will be available in 7.5.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.