Implement SecurityPolicyViolationEvent

Fixed Issue #14314224

Details

Author
Scott H.
Created
Oct 20, 2017
Privacy
This issue is public.
Found in
  • Microsoft Edge
Found in build #
40.15063
Reports
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

The SecurityPolicyViolationEvent interface has been defined since CSP 2.

https://www.w3.org/TR/CSP2/#securitypolicyviolationevent-interface

Debugging and diagnosing CSP issues on the client side is incredibly useful.

Attachments

0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Steven K.”

    • Your
      feedback falls under a feature or
      design change request. 
      I recommend you file your suggestion at the
      uservoice site so others can review your suggestion and vote it up. 
      I see this request has already been
      suggested.

        Add your vote. 

      https://wpdev.uservoice.com/forums/257854-microsoft-edge-developer?query=csp

      Appreciate the request and feedback,

      The MS Edge Team

    • CSP Level 2 support is already listed as completed in MS Edge: https://wpdev.uservoice.com/forums/257854-microsoft-edge-developer/suggestions/9163354-content-security-policy-level-2

      The SecurityPolicyViolationEvent interface is defined in the CSP 2 spec but not implemented: https://www.w3.org/TR/CSP2/#script-interfaces

      Is this not a bug as CSP 2 support is not complete?

    • I see that now.  Thanks for pointing that out.

      Can you tell me the extended version of Windows 10 you used to test the CSP support?  Win + S and type “winver” and hit enter.

      Steve

    • Microsoft Edge Team

      Changed Status to “Fixed”

    • Hi Scott,

      I wanted to follow-up and let you know that the SecurityPolicyViolationEvent is now supported.  I verified this in 16299.371.

      Thanks again for the submission,

      The MS Edge Team

    You need to sign in to your Microsoft account to add a comment.

    Sign in