js/src/jit-test/tests/parser/yield-without-operand.js@129ffea94266
js/src/jit-test/tests/parser/yield-without-operand.js
Sat, 03 Jan 2015 20:18:00 +0100
- author
- Michael Schloh von Bennewitz <michael@schloh.com>
- date
- Sat, 03 Jan 2015 20:18:00 +0100
- branch
- TOR_BUG_3246
- changeset 7
- 129ffea94266
- permissions
- -rw-r--r--
Conditionally enable double key logic according to:
private browsing mode or privacy.thirdparty.isolate preference and
implement in GetCookieStringCommon and FindCookie where it counts...
With some reservations of how to convince FindCookie users to test
condition and pass a nullptr when disabling double key logic.
1 // yield without an operand causes a warning. See bug 885463.
3 load(libdir + "asserts.js");
5 assertWarning(() => Function("yield"), SyntaxError,
6 "yield followed by EOF should cause a warning");
7 assertWarning(() => Function("yield;"), SyntaxError,
8 "yield followed by semicolon should cause a warning");
9 assertWarning(() => Function("yield\n print('ok');"), SyntaxError,
10 "yield followed by newline should cause a warning");
12 assertWarning(() => eval("(function () { yield; })"), SyntaxError,
13 "yield followed by semicolon in eval code should cause a warning");
14 assertWarning(() => eval("(function () { yield })"), SyntaxError,
15 "yield followed by } in eval code should cause a warning");
17 assertNoWarning(() => Function("yield 0;"),
18 "yield with an operand should be fine");
19 assertNoWarning(() => Function("yield 0"),
20 "yield with an operand should be fine, even without a semicolon");
22 print("\npassed - all those warnings are normal and there's no real way to suppress them");
