Skip to content

Commit 035cb43

Browse files
committed
Address feedback from j9t
1 parent 5edc81e commit 035cb43

File tree

2 files changed

+3
-3
lines changed

2 files changed

+3
-3
lines changed

manuscript/conformance-checkers.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -57,12 +57,12 @@ I asked Mike Smith, who contributes to the Validator.nu code base and maintains
5757

5858
The table is truncated at 0.1%.
5959

60-
About 73% of the errors are about mismatched tags (e.g., the first 4 errors, "Bad start tag in "X" in "head".", "Stray start tag "X".", and so on).
60+
About 73% of the errors are about mismatched tags (e.g., the first 4 errors, 'Bad start tag in "X" in "head".', 'Stray start tag "X".', and so on).
6161

6262
The error "No space between attributes." is pretty harmless. In fact it was conforming in HTML4 to omit space between attributes (when they use single or double quotes).
6363

6464
"Duplicate attribute "X"." is pretty high in the list. Only the first attribute is used, subsequent attributes with the same name are ignored.
6565

6666
"Quote "X" in attribute name. Probable cause: Matching quote missing somewhere earlier." means that the author likely somehow messed up quoting around attribute values.
6767

68-
"Self-closing syntax ("`/>`") used on a non-void HTML element. Ignoring the slash and treating as a start tag." means that "`/>`" was incorrectly used on a regular HTML element, which is not supported. It might help to avoid using "`/>`" syntax altogether in HTML (except for SVG and MathML).
68+
'Self-closing syntax ("`/>`") used on a non-void HTML element. Ignoring the slash and treating as a start tag.' means that "`/>`" was incorrectly used on a regular HTML element, which is not supported. It might help to avoid using "`/>`" syntax altogether in HTML (except for SVG and MathML).

manuscript/parser.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1473,7 +1473,7 @@ If the tree builder finds a `frameset` start tag token in the "after head" inser
14731473
└── #text:
14741474
```
14751475
1476-
How does the parser decide if the page is a "frameset" page or a "body" page? Glad you asked.
1476+
How does the parser decide if the page is a "frameset" page or a "body" page?
14771477
14781478
You may recall from the {% ref "parser", "Parsing a simple document" %} section a mention of a frameset-ok flag. This flag determines whether, upon finding a `frameset` start tag token in the "in body" insertion mode, the page should be a frameset page.
14791479

0 commit comments

Comments
 (0)