tag:support.markedapp.com,2011-09-11:/discussions/problems/163825-tocstylecss-causes-issues-with-fontawesome-when-used-in-documentMarked: Discussion 2021-08-13T12:23:09Ztag:support.markedapp.com,2011-09-11:Comment/493318882021-08-11T12:48:12Z2021-08-11T12:48:12Ztocstyle.css causes issues with Fontawesome when used in document<div><p>Turning libraries Marked uses for core functionality would be problematic. That said, the only reason marked has FontAwesome included at all was based on user requests. Stacking must be a new feature?</p>
<p>Thanks,<br>
Brett</p></div>Bretttag:support.markedapp.com,2011-09-11:Comment/493318882021-08-13T07:59:21Z2021-08-13T07:59:21Ztocstyle.css causes issues with Fontawesome when used in document<div><p>Hi Brett,</p>
<p>I'm not sure if it's new or not, but it appears hard coded in toc stylesheet.</p>
<p>I've also run into a problem with the "Prevent orphaned headlines" option where Marked adds or ignores some css instructions when exporting to paginated PDF. Renders fine in the preview and HTML.</p>
<p>The first image is with the option turned on.</p>
<p>This is the css that gets ignored.<br></p>
<pre>
<code>H2 ~ H3 {
padding-top: -6pt !important;
}</code>
</pre></div>dantag:support.markedapp.com,2011-09-11:Comment/493318882021-08-13T12:23:06Z2021-08-13T12:23:06Ztocstyle.css causes issues with Fontawesome when used in document<div><p>When collapse headers is enabled, markup is injected to wrap around headers and their succeeding content. Therefore headers are no longer contiguous in the DOM because they're nested in separate parent containers.</p>
<p>Thanks,<br>
Brett</p></div>Brett