Adding upstream version 86.0.1.upstream/86.0.1upstream

Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>

1 files changed, 27 insertions, 0 deletions

diff --git a/js/src/tests/test262/language/literals/string/legacy-non-octal-escape-sequence-9-strict-explicit-pragma.js b/js/src/tests/test262/language/literals/string/legacy-non-octal-escape-sequence-9-strict-explicit-pragma.js
new file mode 100644
index 0000000000..13fea4f540
--- /dev/null
+++ b/js/src/tests/test262/language/literals/string/legacy-non-octal-escape-sequence-9-strict-explicit-pragma.js
@@ -0,0 +1,27 @@
+// |reftest| error:SyntaxError
+// Copyright (C) 2020 Rick Waldron Inc. All rights reserved.
+// This code is governed by the BSD license found in the LICENSE file.
+/*---
+esid: sec-additional-syntax-string-literals
+description: >
+  String Literals extensions disallowed in strict mode; NonOctalDecimalEscapeSequence 9
+info: |
+  It is possible for string literals to precede a Use Strict Directive that places the enclosing
+  code in strict mode, and implementations must take care to not use this extended definition of
+  EscapeSequence with such literals. For example, attempting to parse the following source text
+  must fail.
+
+  Strict mode is entered via the explicit Use Strict Directive.
+
+  NonOctalDecimalEscapeSequence::one of
+    8 9
+
+flags: [noStrict]
+negative:
+  phase: parse
+  type: SyntaxError
+---*/
+
+$DONOTEVALUATE();
+
+function invalid() { "\9"; "use strict"; }