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 | // Disabling a Debugger object causes events to stop being delivered to it |
michael@0 | 2 | // immediately, even if we're in the middle of dispatching. |
michael@0 | 3 | |
michael@0 | 4 | var g = newGlobal(); |
michael@0 | 5 | var log; |
michael@0 | 6 | |
michael@0 | 7 | var arr = []; |
michael@0 | 8 | for (var i = 0; i < 4; i++) { |
michael@0 | 9 | arr[i] = new Debugger(g); |
michael@0 | 10 | arr[i].num = i; |
michael@0 | 11 | arr[i].onDebuggerStatement = function () { |
michael@0 | 12 | log += this.num; |
michael@0 | 13 | // Disable them all. |
michael@0 | 14 | for (var j = 0; j < arr.length; j++) |
michael@0 | 15 | arr[j].enabled = false; |
michael@0 | 16 | }; |
michael@0 | 17 | } |
michael@0 | 18 | |
michael@0 | 19 | log = ''; |
michael@0 | 20 | g.eval("debugger; debugger;"); |
michael@0 | 21 | assertEq(log, '0'); |