You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If a header has an ID, it would be nice to have that ID applied to a section tag in the rendered HTML in the preview. For example:
markdown
#### foobar{#special}
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
current preview
<divclass="markdown-body"><h2id="foobar">foobar</h2><p>Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.</p></div>
desired preview
<divclass="markdown-body"><sectionid="special"><h2id="foobar">foobar</h2><p>Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.</p></section></div>
Rationale: This is basically what Pandoc does when it converts markdown to html or epub. And that lets us use ID selectors in CSS to apply styles to a particular section of the document:
#special {
font-size: large;
}
Since the "special" id is not in the preview HTML that CSS selector doesn't work in preview. You can only see it after compiling the epub.
The text was updated successfully, but these errors were encountered:
If a header has an ID, it would be nice to have that ID applied to a section tag in the rendered HTML in the preview. For example:
markdown
#### foobar{#special} Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
current preview
desired preview
Rationale: This is basically what Pandoc does when it converts markdown to html or epub. And that lets us use ID selectors in CSS to apply styles to a particular section of the document:
Since the "special" id is not in the preview HTML that CSS selector doesn't work in preview. You can only see it after compiling the epub.
The text was updated successfully, but these errors were encountered: