Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

Jump to bottom

About "Headings and outlines" #8066

Open
mtrootyy opened this issue Jul 3, 2022 · 0 comments
Open

About "Headings and outlines" #8066

mtrootyy opened this issue Jul 3, 2022 · 0 comments

Comments

@mtrootyy
Copy link

mtrootyy commented Jul 3, 2022 •
edited

I have three questions about "4.3.11 Headings and outlines"

  1. How is constructed "implied section" by "Heading content"?

https://html.spec.whatwg.org/multipage/dom.html#heading-content

Heading content defines the heading of a section (whether explicitly marked up using sectioning content elements, or implied by the heading content itself).

The method to be constructed "implied section" is not specified anywhere in the specification.
This should be specified in the specification.
At least the following two points should be clarified.

  • Where is start of "implied section"?
  • Algorithm about where is end of "implied section".
  1. Positionig of "body element" in sectioning.

Because category of "Sectioning root" was obsoluted, this became to be unclear.
Is "body element" top level section in sectioning by "Sectioning content"?
If so, this should be specified in the specification.

  1. Are these two example semantically equivalent?
    (This question is also related to the second question)

Example 1

<body>
  <h1>heading 1-1</h1>
    <p>...</p>
  <h1>heading 1-2</h1>
    <p>...</p>
</body>

Example 2

<body>
<section>
  <h1>heading 1-1</h1>
    <p>...</p>
</section>
<section>
  <h1>heading 1-2</h1>
    <p>...</p>
</section>
</body>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mtrootyy and others