Bug 122581 - Table of contents
Summary: Table of contents
Status: VERIFIED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: iOS Editor (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: Other iOS
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-01-08 21:18 UTC by Nicolas Christener
Modified: 2019-03-22 00:14 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
Google Docs TOC insert (57.33 KB, image/png)
2019-01-08 21:22 UTC, Nicolas Christener
Details
Google Docs TOC update (42.72 KB, image/png)
2019-01-08 21:22 UTC, Nicolas Christener
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Nicolas Christener 2019-01-08 21:18:35 UTC
Description:
Right now it's not possible to insert a "Table of Contents". This should be available but IMHO the LibreOffice dialog is way too complicated.

I think that the way how Google Docs handle this, is enough: just chose one of the templates and your good.

Updating the ToC could/should work with "action buttons" (see #122541) - Google also implemented it in this way.

Steps to Reproduce:
1. Create a writer document with some headings in the iOS app, mark text
2. Try to insert a table of content

Actual Results:
There is no function to insert a toc.

Expected Results:
A user should be able to insert a toc and it should also be possible to update it.


Reproducible: Always


User Profile Reset: No



Additional Info:
Comment 1 Nicolas Christener 2019-01-08 21:22:05 UTC
Created attachment 148155 [details]
Google Docs TOC insert
Comment 2 Nicolas Christener 2019-01-08 21:22:20 UTC
Created attachment 148156 [details]
Google Docs TOC update
Comment 3 Aron Budea 2019-02-12 04:03:02 UTC
Let's confirm.
Comment 4 Nicolas Christener 2019-03-21 10:53:08 UTC
Implemented in 0.1 (23).

It still has some limitations, but I'll create separate issues for those.

Thanks a lot @Collabora!
Comment 5 Aron Budea 2019-03-22 00:14:05 UTC
Let's use status WORKSFORME, since the fixing commit is unknown, thanks for retesting!