You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
| 175 | <section class="footnotes" role="doc-endnotes"> <hr> | Section lacks heading. Consider using “h2”-“h6” elements to add identifying headings to all sections. |
There does not appear to be a way to configure the tag to use (e.g.) 'div' when using HTML5. I'm probably missing something, but I don't see a way to override this without changing footnote.go source file.
<p>That's some text with a footnote.
<supid="fnref:1"><ahref="#fn:1" class="footnote-ref" role="doc-noteref">1</a></sup></p><divclass="footnotes" role="doc-endnotes"><hr />
<ol><liid="fn:1" role="doc-endnote"><p>And that's the footnote.
<ahref="#fnref:1" class="footnote-backref" role="doc-backlink">↩</a></p></li></ol></div>
which uses a div (but also looks like the XHTML version).
The text was updated successfully, but these errors were encountered:
danielfdickinson
changed the title
Using a section without heading causes validation errors
Footnotes: Using a section without heading causes validation errors
Oct 14, 2021
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
goldmark/extension/footnote.go
Line 579 in 829d874
causes
| 175 | <section class="footnotes" role="doc-endnotes"> <hr> | Section lacks heading. Consider using “h2”-“h6” elements to add identifying headings to all sections. |
in W3C http://validator.w3.org/unicorn
There does not appear to be a way to configure the tag to use (e.g.) 'div' when using HTML5. I'm probably missing something, but I don't see a way to override this without changing
footnote.go
source file.I do note that in the referenced https://michelf.ca/projects/php-markdown/extra/#footnotes that the example output given is
which uses a div (but also looks like the XHTML version).
The text was updated successfully, but these errors were encountered: