When building projects locally or on readthedocs with docutils==0.17 that contain rST with bullets (e.g. *), the bullets are not appearing. They do appear with docutils==0.16.
*
Note: In case this isn't globally an issue, it is occurring in edx projects like: https://github.com/edx/edx-toggles/blob/d00ef3bc902d35e4131d374acb5ae1ce00af7b33/requirements/doc.txt#L59.
Thank you for reporting a problem with the new Docutils version. Unfortunately, we cannot help without further information.
Please tell us,
<ul>
whether it is present in any Sphinx-processed rst or only under special conditions.
Bullet-lists¹ work as expected with stock Docutils (rst2html4.py, rst2html5.py, rst2latex.py, ...).
¹ https://docutils.sourceforge.io/docs/user/rst/quickref.html#bullet-lists
² There are some changes in the HTML5 stylesheets which might interfere with custom styles or CSS or templating frameworks.
Thank you. Digging deeper, the HTML is fine and it turns out there is a styling issue for us where the following style now has a higher priority:
li { list-style: none }
Since we are using outdated theme code, I am going to assume this is our own issue for now.
Thank you again for pointing me in the right direction. I think you can close this ticket.
I think this is due to <div class="section"> changing to <section>. Our theme used ".section".
<div class="section">
<section>
Log in to post a comment.
Note: In case this isn't globally an issue, it is occurring in edx projects like: https://github.com/edx/edx-toggles/blob/d00ef3bc902d35e4131d374acb5ae1ce00af7b33/requirements/doc.txt#L59.
Thank you for reporting a problem with the new Docutils version.
Unfortunately, we cannot help without further information.
Please tell us,
<ul>in HTML but no bullets in the browser.²whether it is present in any Sphinx-processed rst or only under special conditions.
Bullet-lists¹ work as expected with stock Docutils (rst2html4.py, rst2html5.py, rst2latex.py, ...).
¹ https://docutils.sourceforge.io/docs/user/rst/quickref.html#bullet-lists
² There are some changes in the HTML5 stylesheets which might interfere with custom styles or CSS or templating frameworks.
Thank you. Digging deeper, the HTML is fine and it turns out there is a styling issue for us where the following style now has a higher priority:
Since we are using outdated theme code, I am going to assume this is our own issue for now.
Thank you again for pointing me in the right direction. I think you can close this ticket.
I think this is due to
<div class="section">changing to<section>. Our theme used ".section".Last edit: Ned Batchelder 2021-06-11