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
When using a TOC (Table of Contents) which we force positioning by command
(:toc: macro and :toc:) somewhere in the document, we do not have a css rule for it which leads to the situation, that a defined toc title will be positioned and rendered like a standard text just underneath the text above. This is only an issue when force positioning, not with automatic positioning.
I have asked the Antora team about this and got the advice to add a css definition for it.
Here is an example code rendered by yarn antora
<div class="paragraph">
<p><code>occ</code> is in the owncloud/ directory; for example <code>/var/www/owncloud</code> on
Ubuntu Linux. <code>occ</code> is a PHP script. <strong>You must run it as your HTTP user</strong>
to ensure that the correct permissions are maintained on your ownCloud
files and directories.</p>
</div>
<div id="toc" class="toc">
<div id="toctitle" class="title">occ Command Directory</div>
As you can see, we reference to a toc id/class, but no definition has been made so far, at least I can´t find one. I am not a css guy, and would ask for help fixing that.
When using a TOC (Table of Contents) which we force positioning by command
(
:toc: macro
and:toc:
) somewhere in the document, we do not have a css rule for it which leads to the situation, that a defined toc title will be positioned and rendered like a standard text just underneath the text above. This is only an issue when force positioning, not with automatic positioning.I have asked the Antora team about this and got the advice to add a css definition for it.
Here is an example code rendered by
yarn antora
As you can see, we reference to a toc id/class, but no definition has been made so far, at least I can´t find one. I am not a css guy, and would ask for help fixing that.
@settermjd @LukasHirt
The text was updated successfully, but these errors were encountered: