47 bytes, text/x-phabricator-request
|Details | Review|
There are a few issues with this test: - it relies on cookies set with a Set-Cookie header from a js file. It clears the cookie service when the test finishes. If you run the test with --verify, the test next fails because the js files are cached and aren't re-fetched, so no cookies are set at all. Clearing the cache in the cleanup function fixes this. - there are a number of places where it waits for loads of URLs in new windows in a way that races with those new windows opening, which breaks the test.
Pushed by firstname.lastname@example.org: https://hg.mozilla.org/integration/autoland/rev/678fecfe0bb1 make browser_firstPartyIsolation.js more reliable, r=johannh
You need to log in before you can comment on or make changes to this bug.