markdown: HTML error with video elements (after version 3.2.2)
I was using version 3.2.2, but after the upgrade I get HTML validation errors with video elements:
'"file:/var/www/html/deponejo/Freak-Spot/output/locutus-de-gnu/index.html":321.4-321.120: error: Unclosed element "video".', '"file:/var/www/html/deponejo/Freak-Spot/output/locutus-de-gnu/index.html":325.45-325.48: error: No "p" element in scope but a "p" end tag seen.', '"file:/var/www/html/deponejo/Freak-Spot/output/locutus-de-gnu/index.html":326.1-326.8: error: Stray end tag "video".'
Input
<video controls poster="https://freakspot.net/wp-content/uploads/2017/01/Bildschirmfoto-vom-2017-02-01-00-58-04.png">
<source src="https://b2aeaa58a57a200320db-8b65b95250e902c437b256b5abf3eac7.ssl.cf5.rackcdn.com/media_entries/12965/A0001-4030.medium.webm" type="video/webm">
<p>Lo siento, tu navegador no soporta HTML 5. Por
favor, cambia o actualiza tu navegador</p>
</video>
Output
<p><video controls poster="https://freakspot.net/wp-content/uploads/2017/01/Bildschirmfoto-vom-2017-02-01-00-58-04.png">
<source src="https://b2aeaa58a57a200320db-8b65b95250e902c437b256b5abf3eac7.ssl.cf5.rackcdn.com/media_entries/12965/A0001-4030.medium.webm" type="video/webm">
<br>
<p>Lo siento, tu navegador no soporta HTML 5. Por
favor, cambia o actualiza tu navegador</p></p>
</video>
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 18 (7 by maintainers)
Commits related to this issue
- Unify all block-level tags. Use the list of tags defined in the core by the md_in_html extension. This ensures that the lists do not diverge and allows users and/or extnesions to expand the list in t... — committed to waylan/markdown by waylan 4 years ago
- Unify all block-level tags. (#1048) Use the list of tags defined in the core by the md_in_html extension. This ensures that the lists do not diverge and allows users and/or extensions to expand the... — committed to Python-Markdown/markdown by waylan 4 years ago
Btw, I just confirmed that adding
video
to the list in the extension solves the reported bug. I could do a quick patch for that, but I suppose we should just do it correctly.