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 | // Iterators from another compartment work with their own .next method |
michael@0 | 2 | // when called from another compartment, but not with the other |
michael@0 | 3 | // compartment's .next method. |
michael@0 | 4 | |
michael@0 | 5 | // FIXME: 'next' should work cross-realm. Bug 924059. |
michael@0 | 6 | |
michael@0 | 7 | load(libdir + "asserts.js"); |
michael@0 | 8 | load(libdir + "iteration.js"); |
michael@0 | 9 | |
michael@0 | 10 | var g = newGlobal(); |
michael@0 | 11 | g.eval("var it = [1, 2]['" + std_iterator + "']();"); |
michael@0 | 12 | assertIteratorNext(g.it, 1); |
michael@0 | 13 | assertThrowsInstanceOf([][std_iterator]().next.bind(g.it), TypeError) |