Remove a large <pre> block full of whitespace. (← force pushed this change out because I understand it's necessity now to ensure correct position scrolling for terminology.)
Added a html comments to explain the <pre> block of whitespace and the empty <span> tags since each are non-obvious.
In #92 we used <span> tags as would seem correct for html, placing the term-to-be-defined within the <span> tags. Here's an example of such a change.
However, for some reason, that breaks mdbook rendering. (Maybe the parser is literally only accepting <span …></span>?)
By reverting this change and making the span tags contain nothing, but immediately prefix the terms-to-be-defined, both the rendering and navigation appear correct both in my local rendering and previous public URL renderings:
<span>tags.Remove a large(← force pushed this change out because I understand it's necessity now to ensure correct position scrolling for terminology.)<pre>block full of whitespace.<pre>block of whitespace and the empty<span>tags since each are non-obvious.In #92 we used
<span>tags as would seem correct for html, placing the term-to-be-defined within the<span>tags. Here's an example of such a change.However, for some reason, that breaks
mdbookrendering. (Maybe the parser is literally only accepting<span …></span>?)The broken rendering is on the current public url and looks like this:
By reverting this change and making the span tags contain nothing, but immediately prefix the terms-to-be-defined, both the rendering and navigation appear correct both in my local rendering and previous public URL renderings: