Sat, 03 Jan 2015 20:18:00 +0100
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.
michael@0 | 1 | // yield without an operand causes a warning. See bug 885463. |
michael@0 | 2 | |
michael@0 | 3 | load(libdir + "asserts.js"); |
michael@0 | 4 | |
michael@0 | 5 | assertWarning(() => Function("yield"), SyntaxError, |
michael@0 | 6 | "yield followed by EOF should cause a warning"); |
michael@0 | 7 | assertWarning(() => Function("yield;"), SyntaxError, |
michael@0 | 8 | "yield followed by semicolon should cause a warning"); |
michael@0 | 9 | assertWarning(() => Function("yield\n print('ok');"), SyntaxError, |
michael@0 | 10 | "yield followed by newline should cause a warning"); |
michael@0 | 11 | |
michael@0 | 12 | assertWarning(() => eval("(function () { yield; })"), SyntaxError, |
michael@0 | 13 | "yield followed by semicolon in eval code should cause a warning"); |
michael@0 | 14 | assertWarning(() => eval("(function () { yield })"), SyntaxError, |
michael@0 | 15 | "yield followed by } in eval code should cause a warning"); |
michael@0 | 16 | |
michael@0 | 17 | assertNoWarning(() => Function("yield 0;"), |
michael@0 | 18 | "yield with an operand should be fine"); |
michael@0 | 19 | assertNoWarning(() => Function("yield 0"), |
michael@0 | 20 | "yield with an operand should be fine, even without a semicolon"); |
michael@0 | 21 | |
michael@0 | 22 | print("\npassed - all those warnings are normal and there's no real way to suppress them"); |