Steps to reproduce: 1. Start Firefox and open the devtool console using Ctrl+Shift+k. 2. Browse to http://fmarier.org/csp/csp-merge.html 3. Open a new non-e10s window. 4. Close the first window. 5. In the e10s window, open the devtool console. 6. Browse to http://fmarier.org/csp/csp-merge.html 7. Open a new normal window. 8. Close the non-e10s window. 9. Open the devtool console. 10. Browse to http://fmarier.org/csp/csp-merge.html Expected: At steps 2, 6 and 10, the devtool console should show that a CSP violation has occurred. Actual: While steps 2 and 6 show the CSP error message, step 10 doesn't.

(In reply to François Marier [:francois] from comment #0) > 5. In the e10s window, open the devtool console. This should read: "5. In the NON-e10s window, open the devtool console."

I am unable to reproduce the bug. It seems that it was solved when the bug https://bug623317.bugzilla.mozilla.org/show_bug.cgi?id=1298680 got solved. I'd like to write a mochitest for the same, as Christoph suggested. Using the idea of asyncTest as used in [1] and change the mochitest [2] for making it work in e10s [1] https://bugzilla.mozilla.org/show_bug.cgi?id=1042253 [2] https://dxr.mozilla.org/mozilla-central/source/devtools/client/webconsole/test/browser_webconsole_bug_770099_violation.js

Upon looking around a bit more through [1], I came across [2] which already has the mochitest I was going to change (browser_webconsole_bug_770099_violation.js). Christoph, should I still submit a mochitest to get familiar with the workflow? [1] https://bugzilla.mozilla.org/show_bug.cgi?id=1042253 [2] https://bugzilla.mozilla.org/page.cgi?id=splinter.html&bug=1042253&attachment=8480294

(In reply to Aashaka [:_7ev3n] from comment #2) > I am unable to reproduce the bug. It seems that it was solved when the bug > https://bug623317.bugzilla.mozilla.org/show_bug.cgi?id=1298680 got solved. That sounds correct. Marking as a dup.