Skip to content

Tags that are void elements and phrasing content should be considered inline elements. #810

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Tags that are void elements and phrasing content should be considered inline elements. #810

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions spec.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2409,8 +2409,8 @@ the string `/>`.\
**End condition:** line is followed by a [blank line].

7. **Start condition:** line begins with a complete [open tag]
(with any [tag name] other than `pre`, `script`,
`style`, or `textarea`) or a complete [closing tag],
(with any [tag name] other than `pre`, `script`, `style`, `textarea`,
`br`, `embed`, `img`, `input` or `wbr`) or a complete [closing tag],
all on a single line, followed by zero or more spaces and tabs,
followed by the end of the line.\
**End condition:** line is followed by a [blank line].
Expand Down