From 52c6a61e3b35b75453c75c7e5cbf76ae12cedeeb Mon Sep 17 00:00:00 2001
From: Jordan Harband <ljharb@gmail.com>
Date: Wed, 24 Mar 2021 09:18:02 -0700
Subject: [PATCH] Editorial: add "Legacy" section (#2125)

 - co-opts prose from Annex B description
 - dfn legacy and add emu-not-ref where appropriate
 - use dash in IDs
 - don't <dfn> legacy; clauses are what is legacy

Co-authored-by: Jordan Harband <ljharb@gmail.com>
Co-authored-by: Michael Ficarra <mficarra@shapesecurity.com>
---
 spec.html | 13 +++++++++++--
 1 file changed, 11 insertions(+), 2 deletions(-)

diff --git a/spec.html b/spec.html
index 298964b4cd3..9fc89c25e36 100644
--- a/spec.html
+++ b/spec.html
@@ -128,8 +128,17 @@ <h1>Conformance</h1>
   <p>A conforming implementation of ECMAScript must not implement any extension that is listed as a Forbidden Extension in subclause <emu-xref href="#sec-forbidden-extensions"></emu-xref>.</p>
   <p>A conforming implementation of ECMAScript must not redefine any facilities that are not implementation-defined, implementation-approximated, or host-defined.</p>
   <p>A conforming implementation of ECMAScript may choose to implement or not implement <dfn>Normative Optional</dfn> subclauses. If any Normative Optional behaviour is implemented, all of the behaviour in the containing Normative Optional clause must be implemented. A Normative Optional clause is denoted in this specification with the words "Normative Optional" in a coloured box, as shown below.</p>
-  <emu-clause id="sec-conformance.normative-optional" example normative-optional>
-    <h1>Example Clause Heading</h1>
+  <emu-clause id="sec-conformance-normative-optional" oldids="sec-conformance.normative-optional" example normative-optional>
+    <h1>Example Normative Optional Clause Heading</h1>
+    <p>Example clause contents.</p>
+  </emu-clause>
+  <p>A conforming implementation of ECMAScript must implement <dfn>Legacy</dfn> subclauses, unless they are also marked as Normative Optional. All of the language features and behaviours specified within Legacy subclauses have one or more undesirable characteristics. However, their continued usage in existing applications prevents their removal from this specification. These features are not considered part of the core ECMAScript language. Programmers should not use or assume the existence of these features and behaviours when writing new ECMAScript code.</p>
+  <emu-clause id="sec-conformance-legacy" example legacy>
+    <h1>Example Legacy Clause Heading</h1>
+    <p>Example clause contents.</p>
+  </emu-clause>
+  <emu-clause id="sec-conformance-legacy-normative-optional" example legacy normative-optional>
+    <h1>Example Legacy Normative Optional Clause Heading</h1>
     <p>Example clause contents.</p>
   </emu-clause>
 </emu-clause>