Show full section headings in table of contents #976

Closed
opened 2026-02-04 23:15:10 +03:00 by OVERLORD · 2 comments
Owner

Originally created by @trwnh on GitHub (Jan 7, 2019).

Describe the feature you'd like

There should be an option to use full section headings and not truncate them.

image

Describe the benefits this feature would bring to BookStack users

In a proper table of contents (as can be found in real books), no entries are truncated. The purpose of the table of contents is to provide an outline of a book or document so that a reader can tell at a glance what that work contains. This cannot be done effectively when the contents are not displayed in full.

Additional context

I would have done this in CSS by adjusting the word wrapping and overflow options, but it seems that the truncated headings are inserted directly with scripts rather than being styled with CSS, so I can't override this with styling alone.

image

Originally created by @trwnh on GitHub (Jan 7, 2019). **Describe the feature you'd like** There should be an option to use full section headings and not truncate them. ![image](https://user-images.githubusercontent.com/10606431/50748903-4d244280-1201-11e9-8b26-1257b1f18c1d.png) **Describe the benefits this feature would bring to BookStack users** In a proper table of contents (as can be found in real books), no entries are truncated. The purpose of the table of contents is to provide an outline of a book or document so that a reader can tell at a glance what that work contains. This cannot be done effectively when the contents are not displayed in full. **Additional context** I would have done this in CSS by adjusting the word wrapping and overflow options, but it seems that the truncated headings are inserted directly with scripts rather than being styled with CSS, so I can't override this with styling alone. ![image](https://user-images.githubusercontent.com/10606431/50749027-f703cf00-1201-11e9-9c47-c7ec9937196f.png)
OVERLORD added the 🛠️ Enhancement🎨 Design💆 UX labels 2026-02-04 23:15:10 +03:00
Author
Owner

@ssddanbrown commented on GitHub (Jun 16, 2019):

Thanks for the suggestion @trwnh.
This is now in master, ready for the next release. Up to 100 characters will be put on the front end (Limit just in-case a parsing error occurs).

To prevent the ellipsing, you'll be able to override the limit-text class.

@ssddanbrown commented on GitHub (Jun 16, 2019): Thanks for the suggestion @trwnh. This is now in master, ready for the next release. Up to 100 characters will be put on the front end (Limit just in-case a parsing error occurs). To prevent the ellipsing, you'll be able to override the `limit-text` class.
Author
Owner

@lifedanceman commented on GitHub (Oct 16, 2025):

Hello! As I see the feature is disabled in new versions. In master branche code is absent at least. How can I manage the feature now? Are there another way to manage one?

@lifedanceman commented on GitHub (Oct 16, 2025): Hello! As I see the feature is disabled in new versions. In master branche code is absent at least. How can I manage the feature now? Are there another way to manage one?
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/BookStack#976