Rendering in Coercion Types subsection is broken

[chordowl]

In the section on type coercions, the list of allowed coercions looks quite wonky (on a recent version of Chrome):

Image

For reference, the rendering on GitHub itself is fine.
I compared the generated HTML and for the first few items, it's identical (for the last few it's only syntax highlighting differences), so it seems like this is a CSS issue (with mdbook?).

[projektir]

The issue seems to arise when, for a given <li> element, there is no text in front of the <code> tag. Setting the <p> element to be inline-block, for example, seems to fix this for those individual cases, but is not favorable in the general case as it makes everything too tall. Perhaps user agent CSS or hljs CSS that tries to force <p> to be a block is causing this. But this doesn't explain why this is happening in Chrome in particular.

This issue seems gone in the current version of Chrome Canary with the user agent CSS remaining the same, so perhaps this is a Chrome bug.

[Havvy]

So, if this goes away in Chrome's (next/current?) beta, then we can close this issue.

[alercah]

I do not see this issue in current Chrome.

[Havvy]

Transient Chrome rendering bug doesn't plague us anymore, so closing.