Skip to content
This repository has been archived by the owner on Jul 30, 2019. It is now read-only.

main cannot be a child of address #1397

Closed
scottaohara opened this issue Apr 21, 2018 · 2 comments · Fixed by #1398
Closed

main cannot be a child of address #1397

scottaohara opened this issue Apr 21, 2018 · 2 comments · Fixed by #1398
Assignees

Comments

@scottaohara
Copy link
Member

The content model for address states:

Flow content, but with no heading content descendants, no sectioning content descendants, and no header, footer, or address element descendants.

However main is also an invalid child of address.

@scottaohara scottaohara self-assigned this Apr 21, 2018
scottaohara added a commit that referenced this issue Apr 21, 2018
fixes #1397
mention that `main` can not be a child of the `address` element.
@scottaohara scottaohara mentioned this issue Apr 21, 2018
chaals pushed a commit that referenced this issue Apr 22, 2018
fixes #1397
mention that `main` can not be a child of the `address` element.
plehegar pushed a commit that referenced this issue Apr 22, 2018
@slemini2033
Copy link

@scottaohara are you sure it's not a mistake about main element?

The main element represents the dominant contents of the document.

so main element could be child of any tag

@scottaohara
Copy link
Member Author

scottaohara commented May 18, 2018

No, it cannot be a child of any tag.

But, per this specific issue, that doesn’t mean that the reverse is untrue. E.g. if the primary content of a document is an address
<main><address>...</address></main>would be appropriate.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants
@scottaohara @slemini2033 and others