Closed
Bug 1336663
Opened 8 years ago
Closed 8 years ago
CSP blocking on sm-drivertools/new-stable-release.html
Categories
(SeaMonkey :: Release Engineering, defect)
SeaMonkey
Release Engineering
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: ewong, Unassigned)
References
Details
The tool that we use to assist SeaMonkey releng to create bugs is:
https://hg.mozilla.org/users/Callek_gmail.com/sm-drivertools/new-stable-release.html,
however, with the recent CSP changes, we are now being CSP blocked and thus not
able to generate any bugs.
Filing this bug to track the fix.
![]() |
Reporter | |
Comment 1•8 years ago
|
||
:gps, could set the CSP header such that it doesn't break this use case?
Thanks
Flags: needinfo?(gps)
Comment 2•8 years ago
|
||
Possible, yes. What CSP policy is needed by this tool?
Depends on: 1319172
Flags: needinfo?(gps)
![]() |
Reporter | |
Comment 3•8 years ago
|
||
(In reply to Gregory Szorc [:gps] (disappearing for a month after 2017-02-10) from comment #2)
> Possible, yes. What CSP policy is needed by this tool?
As it's mainly for jquery stuff, and from my quick glance at the code,
Dynamic Javascript code evaluation.
Am I correct, Callek?
Flags: needinfo?(bugspam.Callek)
Comment 4•8 years ago
|
||
I'm not aware of what exists for CSP policies that are possible/appropriate... sadly...
Flags: needinfo?(bugspam.Callek)
![]() |
Reporter | |
Comment 5•8 years ago
|
||
I have found a different way of running this page. So closing this as wfm.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•