I recognized, that when publishing documents, the list handling is incorrect, when no empty line is above the list in the text attribute of the requirement.
Eventhough a newline is recommended directly above a list by the markdown linter, this is oftentimes ommitted.
When a requirement contains a list with no empty line above, the HTML exporter does not close the <ul> tag correctly after the list, but it is only closed before the next <p> tag.
This leads to a wrong indentation of the subsequent requirements in the HTML output.
In the example given, the </ul> tag should appear directly after the fourth <li> ... </li> line and not only before the next <p> tag occurrs.
I recognized, that when publishing documents, the list handling is incorrect, when no empty line is above the list in the
textattribute of the requirement.Eventhough a newline is recommended directly above a list by the markdown linter, this is oftentimes ommitted.
When a requirement contains a list with no empty line above, the HTML exporter does not close the
<ul>tag correctly after the list, but it is only closed before the next<p>tag.This leads to a wrong indentation of the subsequent requirements in the HTML output.
In the example given, the
</ul>tag should appear directly after the fourth<li> ... </li>line and not only before the next<p>tag occurrs.