joplin
joplin copied to clipboard
TOC regularly replaced by a list
Environment
Joplin version: 2.8.8 Platform: Linux OS specifics: Debian
Steps to reproduce
- Insert
[TOC]
(or[[TOC]]
) at the top of a note - Navigate around other notes, or close the application
- Go back to the note with the
TOC
and see the[TOC]
disappeared and is replace by a markdown list
I am trying to enhance the style of the pdf I export from my notes for professional communication. I used the .table-of-contents
attribute to customize the TOC in the css but when the [TOC]
is replaced by the simple markdown list, the attribute is removed (I checked on the html version of the page), and so the style is broken. The replacement seems to happen randomly but at a high frequency. I can recover the style by deleting manually the list and replace again by [TOC]
but it is quite annoying.
Could be a plugin. Do you have any installed?
I have the 'plugin bundle' installed. I just disabled it, but the problem is still here.
Just to specify, I use the WYSIWYG editor by default, except to add the [TOC]
or some other markdown stuff.
Ok, I was able to replicate it like this
- start a new note in the WYSIWYG mode
- add a few headers
- switch to the Markdown editor
- add
[[TOC]]
- switch back to WYSIWYG
- edit the note
- switch back to MD - the TOC is gone and replaced with links
I think it general Joplin doesn't handle very well editing the same note in both editors, it's not the only issue that can happen when you do try doing this.
This is problematic. Would it be possible to add a button in the WYSIWYG to add a TOC then, to avoid switching between the two editors? I will try to use the double view contently from now to avoid this behavior.
Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? If you require support or are requesting an enhancement or feature then please create a topic on the Joplin forum. This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.
Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, feel free to create a new issue with up-to-date information.