- From: Chris Lilley via GitHub <sysbot+gh@w3.org>
- Date: Wed, 16 Dec 2020 18:57:11 +0000
- To: public-css-archive@w3.org
```
9 errors (and 11 warnings)
38 rules were checked. Hover over the rows below for options.
Tip: review the metadata that was inferred from the document to make sure that there are no errors.
Error
Shortnames differ between This and Latest Versions.
Document identifier information must be presented in a dl list, where each dt element marks up an identifier role ("This Version", "Latest Version", "Previous Version", etc.) and each dd element includes a link whose link text is the identifier.
Error
Deliverer not found. An attribute data-deliverer must be in the SotD
The Working Group(s) id(s) must be listed in a data-deliverer attribute in the section "Status of This Document".
Include this source code:
<p data-deliverer="@@ID1@@,@@ID2@@,...">
Error
Unable to find the deliverer
It must include the name of the W3C group that produced the document. The name must be a link to a public page for the group.
Error
No stability warning paragraph.
It must set expectations about the (in)stability of the document. The recommended text (see also ideas for status sections regarding the stability of group notes) is:
Publication as a Working Group Note does not imply endorsement by the W3C Membership.
Include this source code:
<p>Publication as a Working Group Note does not imply endorsement by the W3C Membership.</p>
Error
Couldn't not determine the patent policy the WG is operating under. Check the WG's charter.
Error
The document must mention the governing process: 15 September 2020
Error
No “status of this document” introduction (eg absent, not using HTTPS, wrong copy).
It must begin with the following boilerplate text:
This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at https://www.w3.org/TR/.
Include this source code:
<p><em>This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the <a href="https://www.w3.org/TR/">W3C technical reports index</a> at https://www.w3.org/TR/.</em></p>
Error
No “status of this document” introduction link to TR (or perhaps not using HTTPS).
It must begin with the following boilerplate text:
This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at https://www.w3.org/TR/.
Include this source code:
<p><em>This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the <a href="https://www.w3.org/TR/">W3C technical reports index</a> at https://www.w3.org/TR/.</em></p>
Error
See rule in context
Report a bug
[3783@197] Bad value “https://drafts.csswg.org/css2/#valdef-border-width-length” for attribute “href” on element “a”: Illegal character in fragment: “<” is not allowed.
HTML validator
All normative representations must validate as HTML5 with the following limitations:
Inline markup for MathML is permitted but should use a (fallback) alternative.
If the HTML5 validator issues content warnings, the publication request must include rationale why the warning is not problematic.
```
--
GitHub Notification of comment by svgeesus
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4715#issuecomment-746828760 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 16 December 2020 18:57:13 UTC