whatwg · mfreed7 · Jul 19, 2021 · Jul 19, 2021 · Jul 19, 2021 · Jul 20, 2021
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -6,7 +6,7 @@ The HTML Standard is quite complex and people notice minor and larger issues wit
 
 We label [good first issues](https://github.com/whatwg/html/labels/good%20first%20issue) that you could help us fix, to get a taste for how to submit pull requests, how the build process works, and so on.
 
-We'd be happy to mentor you through this process. If you're interested and need help getting started, leave a comment on the issue or bug, or ask around [on IRC](https://whatwg.org/irc). The [FAQ](FAQ.md) may also be helpful.
+We'd be happy to mentor you through this process. If you're interested and need help getting started, leave a comment on the issue or bug, or [ask around](https://whatwg.org/chat). The [FAQ](FAQ.md) may also be helpful.
 
 ## Pull requests
 

diff --git a/FAQ.md b/FAQ.md
@@ -82,11 +82,11 @@ Since then, we've realized that much like the [waterfall model](https://en.wikip
 
 ### Is design rationale documented?
 
-Sort of. Often some record of the rationale for a particular design choice can be found within discussions in the GitHub issue tracker, commit logs, or the mailing-list archive or IRC channel archives. Sometimes, there is an explanation in the specification, but doing that everywhere would make the specification huge.
+Sort of. Often some record of the rationale for a particular design choice can be found within discussions in the GitHub issue tracker, commit logs, or the mailing-list archive or [Chat archives](https://whatwg.org/chat#logs). Sometimes, there is an explanation in the specification, but doing that everywhere would make the specification huge.
 
 For a few cases that someone did take the time document, the information can be found at the following locations:
 
-* [Rationale](https://wiki.whatwg.org/wiki/Rationale) — a page that documents some reasons behind decisions in the spec, originally written and maintained by Variable. If anyone wants to help him out, try to grab someone on [IRC](https://wiki.whatwg.org/wiki/IRC); we're always looking for more contributors and this is a good place to start.
+* [Rationale](https://wiki.whatwg.org/wiki/Rationale) — a page that documents some reasons behind decisions in the spec, originally written and maintained by Variable. If anyone wants to help him out, try to find someone via [Chat](https://whatwg.org/chat); we're always looking for more contributors and this is a good place to start.
 * [Why no namespaces](https://wiki.whatwg.org/wiki/Why_no_namespaces)
 * [Why no script implements](https://wiki.whatwg.org/wiki/Why_no_script_implements)
 * [Why not reuse legend](https://wiki.whatwg.org/wiki/Why_not_reuse_legend) or another _mini-header_ element.
@@ -338,6 +338,16 @@ Short of that, there are actually quite a number of ways for people to invent th
 
 HTML allows `<div>` as a grouping element in `<dl>`. See [the `<dl>` specification](https://html.spec.whatwg.org/multipage/#the-dl-element) and [issue #1937](https://github.com/whatwg/html/issues/1937) wherein this was added.
 
+### HTML should add more named character references!
+
+Although this would be convenient, the overall conclusion of the editors and of browser engine implementers is that expanding the [named character references](https://html.spec.whatwg.org/multipage/named-characters.html#named-character-references) list is not worth the cost to the ecosystem:
+
+* The backward-compatibility characteristics of such additions are bad. They do not add new capabilities, since you can already use numeric character references or unescaped code points; they just introduce new ways of writing the same thing, which will fail to display correctly in older browsers.
+
+* The benefits of such features can also be accomplished by preprocessor languages directly. That is, preprocessed languages that compile to HTML, such as Markdown, wiki syntax, JSX, or server-side templating systems, can add these capabilities themselves. The only reason to add these to the browser is to help people writing raw HTML. We do want to support people writing raw HTML, but features for that audience are less impactful than general web platform features, which weighs into the overall decision as to whether to add them or not.
+
+* Most importantly, [the HTML parser is security sensitive](https://github.com/whatwg/html/issues/919#issuecomment-276329905). Any changes in it can cause mismatches between markup producers and markup consumers until everyone is updated to the latest version, which can lead to security bugs. This means that changes to the parser have to add an extreme amount of value to the ecosystem, to overcome this security hazard. Per the above points, our judgment is that adding or modifying named character references does not meet this bar.
+
 ### Where's the harm in adding...?
 
 Every feature we add to the web platform has a cost:
@@ -429,4 +439,4 @@ The Web Forms 2.0 specification was folded into what is now the HTML Standard.
 
 The Web Controls 1.0 specification was overtaken by events and has been abandoned. Its problem space is mostly handled by ARIA and Web Components now.
 
-The DOM Parsing specification was abandoned by the WHATWG because the W3C was doing a better job of maintaining that specification. We do not want to cause confusion in the market place, so when another organization writes a specification that covers the same technology as one of ours, we only continue to publish it if our version is technically superior.
+The DOM Parsing specification was abandoned by the WHATWG because the W3C was doing a better job of maintaining that specification. We do not want to cause confusion in the marketplace, so when another organization writes a specification that covers the same technology as one of ours, we only continue to publish it if our version is technically superior.
diff --git a/PULL_REQUEST_TEMPLATE.md b/PULL_REQUEST_TEMPLATE.md
@@ -11,5 +11,7 @@ Thank you for contributing to the HTML Standard! Please describe the change you
    * Chrome: …
    * Firefox: …
    * Safari: …
+   * Deno (only for timers, structured clone, base64 utils, channel messaging, module resolution, web workers, and web storage): …
+   * Node.js (only for timers, structured clone, base64 utils, channel messaging, and module resolution): …
 
 (See [WHATWG Working Mode: Changes](https://whatwg.org/working-mode#changes) for more details.)
diff --git a/demos/canvas/blue-robot/blue-robot.png b/demos/canvas/blue-robot/blue-robot.png
diff --git a/dev/styles.css b/dev/styles.css
@@ -277,7 +277,7 @@ var > var::after {
 
 .note {
   padding: 3px;
-  background-color: #eee;
+  background-color: #f7f7f7;
 }
 
 .note pre {
@@ -302,7 +302,7 @@ var > var::after {
 
 .css::before {
   content: "CSS:";
-  color: #888888;
+  color: #757575;
   font-size: 1em;
   display: block;
   background: transparent;
@@ -438,7 +438,7 @@ ol.toc li {
 }
 
 ol.toc .secno {
-  color: #888888;
+  color: #757575;
 }
 
 html.index ol.toc li {

diff --git a/images/abstract.png b/images/abstract.png
diff --git a/images/arc1.png b/images/arc1.png
diff --git a/images/arcTo1.png b/images/arcTo1.png
diff --git a/images/arcTo2.png b/images/arcTo2.png
diff --git a/images/arcTo3.png b/images/arcTo3.png
diff --git a/images/baselines.png b/images/baselines.png
diff --git a/images/bidiselect.png b/images/bidiselect.png
diff --git a/images/content-venn.svg b/images/content-venn.svg
diff --git a/images/drawImage.png b/images/drawImage.png
diff --git a/images/fingerprint.png b/images/fingerprint.png
diff --git a/images/focus-tree.png b/images/focus-tree.png
diff --git a/images/im.png b/images/im.png
diff --git a/images/media-stream-1.png b/images/media-stream-1.png
diff --git a/images/media-stream-2.png b/images/media-stream-2.png
diff --git a/images/premultiplied-example-1.png b/images/premultiplied-example-1.png
diff --git a/images/premultiplied-example-3.png b/images/premultiplied-example-3.png
diff --git a/images/premultiplied-example-4.png b/images/premultiplied-example-4.png
diff --git a/images/robots.jpeg b/images/robots.jpeg
diff --git a/images/sample-bdi.png b/images/sample-bdi.png
diff --git a/images/sample-calendar.png b/images/sample-calendar.png
diff --git a/images/sample-card.png b/images/sample-card.png
diff --git a/images/sample-details-1.png b/images/sample-details-1.png
diff --git a/images/sample-details-2.png b/images/sample-details-2.png
diff --git a/images/sample-makeapp.png b/images/sample-makeapp.png
diff --git a/images/sample-meter.png b/images/sample-meter.png
diff --git a/images/sample-not-bdi.png b/images/sample-not-bdi.png
diff --git a/images/sample-progress.png b/images/sample-progress.png
diff --git a/images/sample-range-2a.png b/images/sample-range-2a.png
diff --git a/images/sample-range-2b.png b/images/sample-range-2b.png
diff --git a/images/sample-range-labels.png b/images/sample-range-labels.png
diff --git a/images/sample-range-multiple.png b/images/sample-range-multiple.png
diff --git a/images/sample-range.png b/images/sample-range.png
diff --git a/images/sample-ruby-bopomofo.png b/images/sample-ruby-bopomofo.png
diff --git a/images/sample-ruby-ja.png b/images/sample-ruby-ja.png
diff --git a/images/sample-ruby-pinyin.png b/images/sample-ruby-pinyin.png
diff --git a/images/sample-usemap.png b/images/sample-usemap.png
diff --git a/images/select-country-1.png b/images/select-country-1.png
diff --git a/images/select-country-2.png b/images/select-country-2.png
diff --git a/images/table-scope-diagram.png b/images/table-scope-diagram.png