Problem description: When deleting an empty unnecessary line/bullet point, the indent of the previous bullet point is lost. To me, this is completely unexpected behavior. Steps to reproduce: 1. Download https://dl.dropboxusercontent.com/u/17406199/bugtmp/Bug18.odp 2. Start editing the text field with bulletpoints 3. Press the arrow down key until you are in the very last (empty) line 4. Press the backspace key to delete this unnecessary line/bullet point Current behavior: Indention is lost https://dl.dropboxusercontent.com/u/17406199/bugtmp/Bug18_2.png Expected behavior: The indention should be preserved https://dl.dropboxusercontent.com/u/17406199/bugtmp/Bug7_1.png Thank you very much for all your efforts.
Created attachment 118337 [details] Document to reproduce bug
Created attachment 118338 [details] Screenshot of correct behavior
Created attachment 118339 [details] Screenshot of incorrect behavior
Confirmed. Win 7 Pro 64-bit, Version: 5.0.1.2 (32-bit) Build ID: 81898c9f5c0d43f3473ba111d7b351050be20261 Locale: fi-FI (fi_FI)
Thanks for confirming. Just a sidenote to avoid confusion: While the attachments are correct, the link to the second png is faulty. It should read https://dl.dropboxusercontent.com/u/17406199/bugtmp/Bug18_1.png (In reply to ravingdesi from comment #0) > Problem description: > When deleting an empty unnecessary line/bullet point, the indent of the > previous bullet point is lost. To me, this is completely unexpected behavior. > > Steps to reproduce: > 1. Download https://dl.dropboxusercontent.com/u/17406199/bugtmp/Bug18.odp > 2. Start editing the text field with bulletpoints > 3. Press the arrow down key until you are in the very last (empty) line > 4. Press the backspace key to delete this unnecessary line/bullet point > > Current behavior: > Indention is lost > https://dl.dropboxusercontent.com/u/17406199/bugtmp/Bug18_2.png > > Expected behavior: > The indention should be preserved > https://dl.dropboxusercontent.com/u/17406199/bugtmp/Bug7_1.png > > Thank you very much for all your efforts.
The cause looks like this: The width of numbering at the BBB.... line is 0.30''. That at the last empty line just under BBB... is 0.00". When you delete the line break between the lines from the empty line by using 'Backspace', the attributes of the empty line is inherited, and the numbering width at BBB... becomes 0.00". This is why the second line of BBB... shifts to the left. When you put the cursor at the end of BBB... and delete the line break by using 'Delete', the attribute of BBB... is inherited and the line doesn't shift.
** 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.6 or 5.2.3 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-20161108
Dear ravingdesi, 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
Looks fine in current master 6.5+.
Yup. Seems to work now (Test on 6.3.4.2 on Windows 10).