I've found a bug and checked that ...
Description
With each nested level of definition list, the bottom margin seems to expand.
This appears to be due to display: flow-root (which the expected behaviour shows when removed). I'm not entirely sure why this rule is used to generate new block formatting context, so it's probably not a good solution (unless it were changed to not apply to nested children?).
The behaviour examples shown below is with excessive nesting. My actual use case is not as bad, but noticeable enough that I figured I should raise an issue about it.

???+ info "Syntax"
1. Declaration: `=== [tab-title]`
`[tab-title]`
: Provide a quoted string as the name of the tab. Markdown content is supported.
2. Tab content is provided from the next line onward, assigned by indentation of 4 spaces.
3. There should be a blank line before and after the tab content.
4. Repeat steps for grouping additional content under related tabs.
Expected behavior

Actual behavior

Steps to reproduce the bug
-
Enable and use the def_list markdown extension in mkdocs.yml.
-
Add the markdown below to a doc page and build/preview the rendered output:
Package versions
Current release of the mkdocs-material Docker container.
Project configuration
Standard instance should do the trick, this is affected by mkdocs-material CSS.
System information
Manjaro Linux with Firefox.
I've found a bug and checked that ...
Description
With each nested level of definition list, the bottom margin seems to expand.
This appears to be due to
display: flow-root(which the expected behaviour shows when removed). I'm not entirely sure why this rule is used to generate new block formatting context, so it's probably not a good solution (unless it were changed to not apply to nested children?).The behaviour examples shown below is with excessive nesting. My actual use case is not as bad, but noticeable enough that I figured I should raise an issue about it.
???+ info "Syntax" 1. Declaration: `=== [tab-title]` `[tab-title]` : Provide a quoted string as the name of the tab. Markdown content is supported. 2. Tab content is provided from the next line onward, assigned by indentation of 4 spaces. 3. There should be a blank line before and after the tab content. 4. Repeat steps for grouping additional content under related tabs.Expected behavior
Actual behavior
Steps to reproduce the bug
Enable and use the
def_listmarkdown extension inmkdocs.yml.Add the markdown below to a doc page and build/preview the rendered output:
a : b : c : d : e fPackage versions
Current release of the
mkdocs-materialDocker container.Project configuration
Standard instance should do the trick, this is affected by
mkdocs-materialCSS.System information
Manjaro Linux with Firefox.