Closed Bug 1425993 Opened 2 years ago Closed 2 years ago
Various security violation event tests are going to permafail when Gecko 59 goes to late Beta
[Tracking Requested - why for this release]: Various permafailing tests when the EARLY_BETA_OR_EARLIER ifdef gets flipped on Gecko 59 on Beta. As expected in bug 1037335... TEST-UNEXPECTED-NOTRUN | /content-security-policy/style-src/style-src-imported-style-blocked.html | Should fire a securitypolicyviolation event - expected FAIL TEST-UNEXPECTED-FAIL | dom/tests/mochitest/general/test_interfaces.html | SecurityPolicyViolationEvent should be defined on the global scope (and a bunch more like it)
Assignee: nobody → cfu
Status: NEW → ASSIGNED
Priority: -- → P1
The early/first merge will be Jan. 11th. Tracking so we can make sure to check back in early January.
This is what I'm using to work around it for now on Try with good results.
I'm trying my best to fix SecurityPolicyViolationEvent related follow-up bugs, to see if we can solve the spec issues and enable it in all channels before the merge day. However, I'm not sure if I can finish them on time, so this patch should be necessary. Whom can we ask for review?
Pushed by firstname.lastname@example.org: https://hg.mozilla.org/integration/autoland/rev/4e60eefd78cc Make security violation events Nightly-only and update test expectations accordingly. r=smaug
You need to log in before you can comment on or make changes to this bug.