Better error reporting when CSP not met

Confirmed Issue #9783198 • Assigned to Irfan A.

Details

Author
Mohamed M.
Created
Nov 14, 2016
Privacy
This issue is public.
Found in
  • Microsoft Edge
Found in build #
14.14393
Reports
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

When creating an extension, including remote CSS/JS/Fonts are not possible. Since I came from the Chrome Extension development, I quickly knew that we had to place “content_security_policy” in the manifest. Obviously, it is best for not including remote resources. But there was absolutely no “errors” in the console (extension background) when CSP is not validated.

What I recommend, when a resource failed to load, please state that in the developers console. Right now it isn’t. When CSP doesn’t allow that resource, please state it in the console as well. Such error handling is extremely useful for developers.

Attachments

0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Ibrahim O.”

      Changed Assigned To to “Sebastian P.”

      Changed Assigned To from “Sebastian P.” to “Daniel R.”

      Changed Status to “Confirmed”

      Changed Assigned To from “Daniel R.” to “Akshay P.”

      Changed Status from “Confirmed”

      Changed Assigned To from “Akshay P.” to “Irfan A.”

      Changed Status to “Confirmed”

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

    Sign in