[UI/Rendering] Headers nested inside bullet points break to a new line unexpectedly

[websurfer93]

First of all, thank you for considering the solution for the "Frontmatter rendering" issue discussed previously.

I am writing to report a visual rendering glitch regarding Headers inside Bullet Points.

In my workflow (to maintain a clean visual hierarchy), I often nest headers within list items, like this:

- # Heading 1
    - ## Heading 2
        - ### Heading 3
            - Sample [[Text]]

In the Influx view, the header text drops to the next line below the bullet point, creating a large, ugly vertical gap. It seems the header is being rendered as a block element starting on a new line rather than inline with the bullet.

The header should be rendered inline, immediately after the bullet point, just as it appears in the standard Obsidian preview or other outliner tools.

This is likely a CSS display issue where the header tags (h1-h6) inside the list item (li) need to be set to display: inline; or display: inline-block; within the Influx container context to prevent the line break.

Thanks for your hard work!

[semanticdata]

@websurfer93 I just had the best laugh thanks to you. I think I finally solved this issue. I just assumed the text in your screenshots was from like your vault and never stopped to read it beyond what you wrote in the issue itself. Well, here I am, recreating what you did to test the fix and finding you did something similar in your screenshots. Idk. It was really funny to me that I just skipped over that.

Getting back on track; this was a bit more complicated than it looked like. I spent more time than I'd like to admit trying to find out why we were inserting elements in new lines. It seems somewhere in Obsidian certain elements have some styling that is difficult to remove. The plugin creator originally tackled this by striping <p> elements out of lists, because otherwise even "just text" creates it's own line.

I have been working on a brand new refactored version 3.0.0 that originally started as a small set of fixes and ended in a big reorganization that I hope makes it way easier to make changes like this in the future. We have a new data pipeline for handling CM6 editor elements and no longer use innerHTML which seemed to have issues with passing styles.

Thanks again so much for your feedback! Look forward to the new version once it's ready for release. I still have work I want to do before it's finished. It fixes a lot of the currently open issues.