Exploring TOC Issues

Contribute UX

AI-generated summary

The discussion Exploring TOC Issues revolves around problems encountered when adding text after a Table of Contents (TOC). Moin observes that text on the following line becomes a single line and has issues with formatted code, even when using code tags. Additionally, using a <mark> without an end causes the text to remain dark in dark themes.

Moin and Firepup650 provide examples of these issues, including:

  • Text becoming a single line after a TOC
  • Formatted code not being displayed correctly
  • <mark> tags causing dark text in dark themes

Lhc_fl suggests that the issue may be due to mixing Markdown and HTML, causing the second line to be recognized as part of the HTML.

1

I think there are some strange issues when you add text in the line following the TOC. You need to look at the raw post to spot all the problems.

I added a TOC in the line above. Now, I start a new line, but the text shows as one line. There are problems with formatted code, so you cannot see `` or ``` ``` . Although I used code tags. When I use a without an end and leave a line free,

the text below remains dark in dark themes.
2 Likes
Data-theme-toc="true" should be placed at the top of a post in it's own paragraph
3

I’ve seen a similar issue to this before, and I have a few scenarios for it:

1. <ex> Then text:

Some `unformatted` text **here**. This is a different line. `` ``` ```

A double newline fixes this.

2. Text before <ex>

formatted before

Still formatted after <With code>

<With long code>
1 Like
4
This is just the bug(feature?) of mixing markdown and HTML. The second line is recognized as a part of html. 
<div>
This is just the bug(feature?) of mixing markdown and HTML.
The second line is recognized as a part of html.