Repository navigation
Don't put <p> around summary tag inside details with markdown flag set? #1079
Description
The summary tag is a special tag inside details that I think should be ignored when processing internal markdown.
from markdown import markdown
from pprint import pprint
a = """
<details markdown="1">
<summary><b>Click to expand table</b></summary>
| Entity | Count |
|:------------------------------------|--------:|
| Thing 1 | 16 |
| Thing 2 | 9 |
</details>
"""
pprint(markdown(a, extensions=["extra"]))' <details>\n'
'<p><summary><b>Click to expand table</b></summary></p>\n'
'<table>\n'
'<thead>\n'
'<tr>\n'
'<th align="left">Entity</th>\n'
'<th align="right">Count</th>\n'
'</tr>\n'
'</thead>\n'
'<tbody>\n'
'<tr>\n'
'<td align="left">Thing 1</td>\n'
'<td align="right">16</td>\n'
'</tr>\n'
'<tr>\n'
'<td align="left">Thing 2</td>\n'
'<td align="right">9</td>\n'
'</tr>\n'
'</tbody>\n'
'</table>\n'
'</details>'Note here that there are <p></p> around the summary, but IMO there should not be.
Activity
waylan commentedon Nov 30, 2020
Can you point to support for this in the HTML5 spec?
Sent with GitHawk
fiendish commentedon Dec 1, 2020
I don't understand the request. Support for what, the summary tag?
See: https://html.spec.whatwg.org/multipage/interactive-elements.html#the-summary-element
Also: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/summary
facelessuser commentedon Dec 1, 2020
summaryis being treated as inline from what I can tell. You can modify the elements treated as block in a plugin though, or you can modify the block elements of theMarkdowninstance directly: https://github.com/Python-Markdown/markdown/blob/master/markdown/core.py#L75. Now, could we treatsummaryas a block element by default? That is up to @waylan, but this can be worked around.Alternatively, you could consider using a plugin for details: https://facelessuser.github.io/pymdown-extensions/extensions/details/.
waylan commentedon Dec 1, 2020
Looking at the spec it seems that the
summarytag is only valid as the first child of adetailtag and can only contain elements which aptag can contain. Any other use would be invalid. Therefore...detail. If a document author uses it in that way that is on them. In other words we don't need to be concerned with using a different parsing behavior outside of the very limited valid use-case.pwould cause it to not be the first child ofdetailand therefore it would always be invalid to wrap it in aptag.Given the above, yes,
summaryshould be added to the default list of block-level elements. It should also be added to the list of span_tags of themd_in_htmlextension to control the default behavior when it is given amarkdown="1"attribute.Ensure <summary> tags are parsed correctly.
Ensure <summary> tags are parsed correctly.