We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
aside
section
figure
HTML5 has some newer (compared to HTML 4) sectioning elements that should be displayed as blocks rather than inline:
<!DOCTYPE html> <title>HTML5 Block-level Elements</title> <header> Header </header> <main> Main <aside> Aside </aside> <section> Section <figure> Figure <figcaption> Figcaption </figcaption> </figure> </section> </main> <footer> Footer </footer>
In contemporary graphical browsers, this displays as follows:
In ELinks it displays as:
Relevant specification (§ 15 Rendering) – Flow content:
address, blockquote, center, dialog, div, figure, figcaption, footer, form, header, hr, legend, listing, main, p, plaintext, pre, search, xmp { display: block; } blockquote, figure, listing, p, plaintext, pre, xmp { margin-block: 1em; } blockquote, figure { margin-inline: 40px; }
Sections and headings:
article, aside, h1, h2, h3, h4, h5, h6, hgroup, nav, section { display: block; }
Rendering these unrecognized HTML5 elements inline may produce confusing results.
Somewhat related to #341.
The text was updated successfully, but these errors were encountered:
[html] Add line break after aside, figure, figcaption and section. Refs
c63931e
#347
Now they are rendered similar to div.
Sorry, something went wrong.
Are header and footer handled explicitly? (didn't see them listed in the element_info array)
header
footer
<section> <header> Header </header> Section <footer> Footer </footer> </section>
[html] line break after footer and header. Refs #347
2aed70b
Now header and footer are also similar to div. Unknown tags are rendered inline (at least I think so).
No branches or pull requests
HTML5 has some newer (compared to HTML 4) sectioning elements that should be displayed as blocks rather than inline:
In contemporary graphical browsers, this displays as follows:
In ELinks it displays as:
Relevant specification (§ 15 Rendering) – Flow content:
Sections and headings:
Rendering these unrecognized HTML5 elements inline may produce confusing results.
Somewhat related to #341.
The text was updated successfully, but these errors were encountered: