Bug 95909 - Tab create a new line in Table of Contents/ Index
Summary: Tab create a new line in Table of Contents/ Index
Status: RESOLVED DUPLICATE of bug 89505
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.4.5.2 release
Hardware: All macOS (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-11-18 14:56 UTC by DonLocke
Modified: 2015-12-22 07:20 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
example (16.73 KB, application/vnd.oasis.opendocument.text)
2015-11-18 14:56 UTC, DonLocke
Details
Screenshot (133.59 KB, image/png)
2015-11-19 07:49 UTC, DonLocke
Details
after (164.83 KB, image/png)
2015-11-19 07:54 UTC, DonLocke
Details

Note You need to log in before you can comment on or make changes to this bug.
Description DonLocke 2015-11-18 14:56:04 UTC
Created attachment 120628 [details]
example

Works in LO 4.2.8
Do not work in: 4.4.5, or 5...

The Index/ Table break lines if you use Tab-Stop.

LO 4.2.8
Open the example file with LO 4.2.8 => right mouse click => update index/table
=>Everything's OK!

LO 4.4.5, or 5.0.3
Open the example file with LO 4.2.8 => right mouse click => update index/table
=>completely wrecked

Open the File in LO 4.2.8 again, and everithing is fine.

The Bug is still present in:
Version: 5.0.4.0.0+
Build ID: de7a50d627250fb9bb6c15f6b601d846566040d5
TinderBox: MacOSX-x86_64@49-TDF, Branch:libreoffice-5-0, Time: 2015-11-18_13:30:48
Locale: de-DE (de.UTF-8)

Look likely the bug:94318, but it is not the same.
Comment 1 Alex Thurgood 2015-11-18 17:48:48 UTC
@Don : sorry,I don't understand what you are trying to do.

1) Download the file attached to bug report
2) Opened in LO4242
3) Place cursor in TOC (mouse click positioning), e.g. at end of the line of an entry, press Tab key

4) Error message : "Read only content cannot be changed. No modifications will be accepted."

So, unless your instructions are incomplete, or I am doing something wrong, I'm afraid I can't reproduce your problem. Please provide systematic reproducible instructions.


Setting NEEDINFO
Comment 2 DonLocke 2015-11-19 07:49:32 UTC
Created attachment 120648 [details]
Screenshot
Comment 3 DonLocke 2015-11-19 07:53:51 UTC
@Alex, no problem my english may be horrible.

Now I try the same in Version: 5.1.0.0.alpha1, the Bug is still present.

Right klick on "Index/Table" => Update Index/Table => The "Index/Table" is broken.
Comment 4 DonLocke 2015-11-19 07:54:25 UTC
Created attachment 120649 [details]
after
Comment 5 Alex Thurgood 2015-11-19 13:37:46 UTC
(In reply to DonLocke from comment #3)


@Don : not horrible at all, just an incomplete description :-)

Going back to your original post, you write :

"The Index/ Table break lines if you use Tab-Stop."

What do you mean by this ?
If I try to use the Tab key when the mouse cursor is located within the Index/Table of Contents, I get the error message I mentioned in my first reply.



> 
> Right klick on "Index/Table" => Update Index/Table => The "Index/Table" is
> broken.

Surely, you have to have changed something in the index for that to have any effect ?

Alex
Comment 6 Alex Thurgood 2015-11-20 16:32:28 UTC
Tested on

Version: 4.2.4.2
Build ID: 63150712c6d317d27ce2db16eb94c2f3d7b699f8

When I edit one of the entries, e.g. entry number 2, and insert an extra tab space, then right mouse button click on the TOC and choose "Update TOC", all of the contents of the TOC disappear, leaving only the heading Table of Contents !
Comment 7 Alex Thurgood 2015-11-20 16:39:54 UTC
Same behaviour in 

Version: 4.1.4.2
Build ID: 0a0440ccc0227ad9829de5f46be37cfb6edcf72

Same behaviour in 5022

Irrespective of tha changes I make to the entries in the document, as soon as I click on update, or deactivate the protection of the TOC (in the document provided by the reporter, the TOC is protected), I lose the TOC and am left with just a general TOC heading entry.
Comment 8 Alex Thurgood 2015-11-20 16:45:39 UTC
I can't confirm this particular bug, as I see completely different behaviour, which is equally as buggy. Will check whether there is already a report for this.

@Don : I'm using OSX 10.11.1, which version of OSX are you using ?
Comment 9 Alex Thurgood 2015-11-20 17:04:33 UTC

*** This bug has been marked as a duplicate of bug 89505 ***