~dricottone/noticable

008cdd48c1086aa6c0ed8951cfca21cfed3b1b0c — Dominic Ricottone 3 years ago f394681
Washing my hands of content security policy

Why do I even need to do this for a local application? This isn't a
website. Content security policy is pointless anyway.

Node packages depend on all sorts of styling and evaluation. It isn't
possible to set a content security policy without many many exceptions.
At minimum, Monca seems to need unsafe-inline styling and unsafe-eval
scripting.
1 files changed, 0 insertions(+), 1 deletions(-)

M index.html
M index.html => index.html +0 -1
@@ 7,7 7,6 @@
    <meta name="description" content="" />
    <link rel="stylesheet" href="node_modules/github-markdown-css/github-markdown.css" />
    <link rel="stylesheet" href="style.css" />
    <meta http-equiv="Content-Security-Policy" content="default-src 'self'; style-src 'unsafe-inline' file:" />
  </head>
  <body>
    <div class="sidebar">