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 | // Specifying an owning element in a cross-global evaluation shouldn't crash. |
michael@0 | 2 | // That is, when 'evaluate' switches compartments, it should properly wrap |
michael@0 | 3 | // the CompileOptions members that will become cross-compartment |
michael@0 | 4 | // references. |
michael@0 | 5 | |
michael@0 | 6 | evaluate('42 + 1729', { global: newGlobal(), element: {} }); |