Bug 52065 - FORMATTING: LO loads and saves tab information incorrectly
Summary: FORMATTING: LO loads and saves tab information incorrectly
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected)
3.5.3 release
Hardware: Other All
: medium normal
Assignee: Not Assigned
Keywords: bibisected, bisected, regression
Depends on:
Blocks: Tab-Character
  Show dependency treegraph
Reported: 2012-07-13 18:36 UTC by Milos Sramek
Modified: 2018-10-08 02:47 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:

doc version of the buggy file (23.50 KB, application/msword)
2012-07-13 18:36 UTC, Milos Sramek
Document that show the TABs bug. (14.03 KB, application/vnd.oasis.opendocument.text)
2012-12-18 10:34 UTC, ydutrieux

Note You need to log in before you can comment on or make changes to this bug.
Description Milos Sramek 2012-07-13 18:36:08 UTC
Created attachment 64186 [details]
doc version of the buggy file
Comment 1 Milos Sramek 2012-07-13 19:05:10 UTC

There are two "signature" placeholders in the attached doc file - the right has three text lines. When loaded in LO, only second and third appear, the text "Pečiatka zamestnávateľa" is hidden. It appears, however, if the tab after "Podpis zamestnanca" (in the left signature) is deleted (and vanishes if the tab is inserted again). So, it appears that the missing text is "behind a corner".

If opened in MSO and Abiword, all three lines are displayed.

If the file is after loading in LO saved in the odf format, the line is still missing when loaded in LO, but is OK when opened in MSO and Abiword.
Comment 2 ydutrieux 2012-12-18 10:34:49 UTC
Created attachment 71719 [details]
Document that show the TABs bug.

Confirmed in libo 4 Version (Build ID: 87906242e87d3ddb2ba9827818f2d1416d80cc7)
Unbuntu 12.04 64bits

what it do : The Third tab is over the line end depending on the size of text of previous tab (when centered ? ) - text could be inserted but not visible.

Document joined is original of libo with same bug.
Comment 3 bfoman (inactive) 2013-01-28 12:53:11 UTC
NEW per comment 2.
Comment 4 QA Administrators 2015-04-19 03:21:54 UTC Comment hidden (obsolete)
Comment 5 Milos Sramek 2015-04-19 07:35:22 UTC
the bug is still present in Version: and
Comment 6 QA Administrators 2016-09-20 09:24:29 UTC Comment hidden (obsolete)
Comment 7 Milos Sramek 2016-09-21 07:43:07 UTC
The bug is still present in master
It is a regression present since LO36, not present in LO33
ApacheOO41 is also OK

Bibisected using the file BUG52065.odt:

7a864e30bffdf16060a3e8abe6d1f6853e841ce7 is the first bad commit
commit 7a864e30bffdf16060a3e8abe6d1f6853e841ce7
Author: Bjoern Michaelsen <bjoern.michaelsen@canonical.com>
Date:   Wed Apr 25 10:25:21 2012 +0200

    commit 4ff7252375b7b85eafbf176ca4e9184cc392d980
    Author:     Michael Stahl <mstahl@redhat.com>
    AuthorDate: Sun Feb 12 21:42:44 2012 +0100
    Commit:     Michael Stahl <mstahl@redhat.com>
    CommitDate: Mon Feb 13 00:25:03 2012 +0100

# bad: [423a84c4f7068853974887d98442bc2a2d0cc91b] source-hash-c15927f20d4727c3b8de68497b6949e72f9e6e9e
# good: [65fd30f5cb4cdd37995a33420ed8273c0a29bf00] source-hash-d6cde02dbce8c28c6af836e2dc1120f8a6ef9932
git bisect start 'latest' 'oldest'
# bad: [e02439a3d6297a1f5334fa558ddec5ef4212c574] source-hash-6b8393474974d2af7a2cb3c47b3d5c081b550bdb
git bisect bad e02439a3d6297a1f5334fa558ddec5ef4212c574
# bad: [8f4aeaad2f65d656328a451154142bb82efa4327] source-hash-1885266f274575327cdeee9852945a3e91f32f15
git bisect bad 8f4aeaad2f65d656328a451154142bb82efa4327
# bad: [369369915d3582924b3d01c9b01167268ed38f3b] source-hash-45295f3cdceb4c289553791071b5d7f4962d2ec4
git bisect bad 369369915d3582924b3d01c9b01167268ed38f3b
# good: [351622aec2dff3cc3bbbb020ad0097c4322d2a21] source-hash-2c4537471c932b65e6f72e41881b505c4bbad12c
git bisect good 351622aec2dff3cc3bbbb020ad0097c4322d2a21
# bad: [378efb6e51212a05d1bd4b85c916eec5753c1744] source-hash-d453788ac0476cc02b929b0907718ca771d6d956
git bisect bad 378efb6e51212a05d1bd4b85c916eec5753c1744
# good: [1a3c4b54a8782fe0f4bdba221e87012a92e4d323] source-hash-a330f38093e2643a26239557050561afae9ff23d
git bisect good 1a3c4b54a8782fe0f4bdba221e87012a92e4d323
# bad: [5313c0086bde1a424c33b54120f14c4c79989cf7] source-hash-243fbda523cb71d0919539081d286eec4717ce15
git bisect bad 5313c0086bde1a424c33b54120f14c4c79989cf7
# bad: [45f31a35bb84d90093b303692f7424e63043f9aa] source-hash-f1c162967f032fcc5e4859f67c5b614c5dd19642
git bisect bad 45f31a35bb84d90093b303692f7424e63043f9aa
# bad: [7a864e30bffdf16060a3e8abe6d1f6853e841ce7] source-hash-4ff7252375b7b85eafbf176ca4e9184cc392d980
git bisect bad 7a864e30bffdf16060a3e8abe6d1f6853e841ce7
# good: [9ee4ea8545fce94fc73af72ea32cc77621dedb3e] source-hash-f484e0b07820d5772376aa75bc0f823f1e77e2f2
git bisect good 9ee4ea8545fce94fc73af72ea32cc77621dedb3e
# first bad commit: [7a864e30bffdf16060a3e8abe6d1f6853e841ce7] source-hash-4ff7252375b7b85eafbf176ca4e9184cc392d980
Comment 8 Michael Stahl (CIB) 2017-06-22 14:15:32 UTC
bibisect range:

regression from:

commit 36c905d8c2874f6f984d5fbbc07784ec20c43524
Author:     Cédric Bosdonnat <cedric.bosdonnat.ooo@free.fr>
AuthorDate: Fri Feb 10 21:57:54 2012 +0100

    fdo#45908: Cleaning up the tabs too early can cause loops
Comment 9 QA Administrators 2018-10-08 02:47:36 UTC
** 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