Bug 58311 - FORMATTING: Tab Causes two new Lines
Summary: FORMATTING: Tab Causes two new Lines
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: Other All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks: Paragraph-Tab-Stops
  Show dependency tree / graph
 
Reported: 2012-12-14 18:09 UTC by Harald Koester
Modified: 2023-04-06 03:24 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Harald Koester 2012-12-14 18:09:49 UTC 
Problem description: 

Steps to reproduce:
(1) Open new text document.
(2) Define a left tab about 2 cm left from the right margin.
(3) Insert one word at the beginning of the first line.
(4) Insert tab. The Cursor jumps to the tab position of step (2).
(5) Insert a word, which is longer than 2 cm. When the right margin is arrived an empty line is inserted and the word is positioned at the beginning of the third line !!! Expected behaviour: No empty line and word is positioned at the beginning of the second line.
(6) Try to correct this behaviour: Set cursor at the beginning of the second line and then Backspace. It does not delete the second line but the last letter of the word in the first line.

              
Operating System: Windows 7
Comment 1 Jorendc 2012-12-16 23:58:51 UTC 
Thanks for submitting this bug!

I can confirm this behavior with Mac OSX 10.8.2

LibreOffice 3.5.7.2 Build ID: 3215f89-f603614-ab984f2-7348103-1225a5b
LibreOffice 3.6.4.3 (Build-id: 2ef5aff)
LibreOffice Version 4.0.0.0.beta1 (Build-id: 87906242e87d3ddb2ba9827818f2d1416d80cc7)
TinderBox: MacOSX TDF Release, Branch:libreoffice-4-0, Time: 2012-12-05_22:13:37
Comment 2 QA Administrators 2015-01-05 17:51:48 UTC Comment hidden (obsolete)
Comment 3 Harald Koester 2015-01-06 11:54:21 UTC Comment hidden (obsolete)
Comment 4 QA Administrators 2016-01-17 20:03:39 UTC Comment hidden (obsolete)
Comment 5 Harald Koester 2016-01-18 18:37:20 UTC Comment hidden (obsolete)
Comment 6 QA Administrators 2017-03-06 14:11:53 UTC Comment hidden (obsolete)
Comment 7 Harald Koester 2017-03-15 15:16:46 UTC 
Bug still exists in version 5.3.0 (Win7).
Bug already exists in version 3.3.0. Hence inherited from OOo.
Comment 8 QA Administrators 2018-03-16 03:36:10 UTC Comment hidden (obsolete)
Comment 9 Harald Koester 2018-03-19 22:18:20 UTC Comment hidden (obsolete)
Comment 10 QA Administrators 2019-03-20 03:49:47 UTC Comment hidden (obsolete)
Comment 11 Harald Koester 2019-04-05 15:40:38 UTC Comment hidden (obsolete)
Comment 12 Harald Koester 2019-04-05 15:52:16 UTC 
Bug still exists in version 6.2.2 (64 Bit, Win 10).
Comment 13 QA Administrators 2021-04-05 03:53:41 UTC Comment hidden (obsolete)
Comment 14 Timur 2021-04-05 14:26:42 UTC 
please attach sample ODT and check for duplicates in newer bugs.
Comment 15 QA Administrators 2023-04-06 03:24:17 UTC 
Dear Harald Koester,

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