Chrome Packaged App: Refused to evaluate a string as JavaScript because 'unsafe-eval' #612

himulawang · 2014-07-07T02:48:28Z

Seems this problem come back again. #252

Chromium 36.0.1985.67 (Developer Build 277752)
OS Linux
Blink 537.36 (@173750)
JavaScript V8 3.26.31
Dart 1.5.2
Flash (Disabled)
User Agent Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/36.0.1985.67 (Dart) Safari/537.36
Command Line ./chrome --flag-switches-begin --enable-experimental-web-platform-features --flag-switches-end

dependencies:
  browser: any
  chrome: any
  logging: any
  paper_elements: any
  polymer: any

Refused to evaluate a string as JavaScript because 'unsafe-eval' is not an allowed source of script in the following Content Security Policy directive: "default-src 'self' chrome-extension-resource:". Note that 'script-src' was not explicitly set, so 'default-src' is used as a fallback.
observe.js:988
(anonymous function) observe.js:988
(anonymous function) observe.js:992
(anonymous function) wrappers.js:37

<!DOCTYPE html>

<html>
<head>
  <title>PRM</title>

  <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0">
  <meta name="mobile-web-app-capable" content="yes">
  <meta name="apple-mobile-web-app-capable" content="yes">

  <!--
  <link rel="stylesheet" href="styles.css">
  -->

  <script src="packages/web_components/platform.js"></script>
  <script src="packages/web_components/dart_support.js"></script>

  <link rel="import" href="packages/paper_elements/paper_button.html">
  <link rel="import" href="packages/core_elements/core_drawer_panel.html">

  <style>
    body {
      font-family: sans-serif;
      color: #FFF;
      height: 100%;
    }

    [drawer] {
      background-color: #B99588;
      border-right: 1px solid #ccc;
    }

    [main] {
      height: 100%;
      background-color: #4F7DC9;
    }

    button {
      width: 160px;
      height: 40px;
      font-size: 16px;
      margin: 8px;
    }

    core-drawer-panel[narrow] button {
      display: inline-block
    }
  </style>
</head>

<body unresovled fullbleed>
  <core-drawer-panel>

    <div drawer>
      Drawer Panel
      <paper-button label='OK'>OK</paper-button>
    </div>

    <div main>
      Main Panel
      <button>toggle drawer</button>
    </div>

  </core-drawer-panel>

  <script type="application/dart" src="main.dart"></script>
  <script src="packages/browser/dart.js"></script>
</body>
</html>

Anybody has the same problem?

jmesserly · 2014-07-07T18:59:13Z

Hi @himulawang, I fixed this already in googlearchive/observe-js@fc8d439

The Dart web_component package is updated in https://codereview.chromium.org/355133002/

Also, a few general notes:

"any" is a dangerous version constraint. It can select very old versions. It's much better to choose a recent version yourself.
--enable-experimental-web-platform-features should not be needed anymore.

himulawang · 2014-07-08T02:42:06Z

Thank you for your notes & fixing this problem so fast @jmesserly

jmesserly · 2014-07-08T04:30:29Z

No problem! I wanted to point you at one additional problem we found today: https://github.com/Polymer/polymer-dev/issues/42 ... it only happens if you are using "noscript" elements.

Dumbris · 2014-07-11T09:46:25Z

As i understand this fix does not availiable on https://pub.dartlang.org/packages/web_components now.

Could you tell please, how to use the lastest dev version of web_components?

I rebuild platform.js from github (via https://github.com/polymer/tools). Then override platform* files in dart source tree dart/pkg/web_components/lib with newly builded files.
Then add to pubspec.yaml in my project with
dependency_overrides:
web_components:
path: ../path/to/web_components

But I see the same errors in console "Refused to execute inline script because it violates the following Content Security Policy directive: "default-src 'self' chrome-extension-resource:". Either the 'unsafe-inline' keyword, a hash ('sha256-...'), or a nonce ('nonce-...') is required to enable inline execution. Note also that 'script-src' was not explicitly set, so 'default-src' is used as a fallback."
So problem not gone.

I try to use paper-button polymer elements in chrome packaged app.
Project https://github.com/Dumbris/test_polymer_paper_elements_chrome_app can be used as minimal working example to show the problem.

Dumbris · 2014-07-11T14:31:52Z

I found solution. After dart2js run vulcanize index.html --csp.
But in this case is impossible to use dartium and dartEditor for debug.

zoechi · 2014-07-11T15:38:16Z

Have you tried what I suggested on your SO question http://stackoverflow.com/questions/24620604
The Polymer transformer does mostly the same as vulcanize. Launching the app from DartEditor uses pub serve to serve the files to Dartium and pub serve invokes configured transformers. Or doesn't that apply for the JavaScript embedded in the paper-elements?

Dumbris · 2014-07-11T16:24:18Z

Yes, I use
transformers:

polymer:
entry_points: web/test_polymer_paper_elements_chrome_app.html
csp: 'true'
chrome

see https://github.com/Dumbris/test_polymer_paper_elements_chrome_app/blob/master/pubspec.yaml

but it is not enough, in practice. I suppose because dart paper_elements import a html files with polymerJS based paper_elements

prateekjassal · 2014-07-29T09:29:53Z

How do we fix this in a Chrome packaged app without using Dart ?

robdodson · 2014-07-29T16:06:38Z

Running the app through vulcanize with the --csp flag should fix it.

Give this a shot: github.com/polymerlabs/polymerchromeapp

On Tue, Jul 29, 2014 at 2:30 AM, Prateek Jassal notifications@github.com
wrote:

How do we fix this in a Chrome packaged app without using Dart ?

—
Reply to this email directly or view it on GitHub
#612 (comment).

jmesserly closed this as completed Jul 7, 2014

arv mentioned this issue Jul 28, 2014

observe.js eval('%RunMicrotasks()') googlearchive/polymer-tutorial#17

Closed

dborkan mentioned this issue Mar 12, 2015

Polymer requires unsafe-eval CSP UWNetworksLab/uProxy-p2p#679

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Chrome Packaged App: Refused to evaluate a string as JavaScript because 'unsafe-eval' #612

Chrome Packaged App: Refused to evaluate a string as JavaScript because 'unsafe-eval' #612

himulawang commented Jul 7, 2014

jmesserly commented Jul 7, 2014

himulawang commented Jul 8, 2014

jmesserly commented Jul 8, 2014

Dumbris commented Jul 11, 2014

Dumbris commented Jul 11, 2014

zoechi commented Jul 11, 2014

Dumbris commented Jul 11, 2014

prateekjassal commented Jul 29, 2014

robdodson commented Jul 29, 2014

Chrome Packaged App: Refused to evaluate a string as JavaScript because 'unsafe-eval' #612

Chrome Packaged App: Refused to evaluate a string as JavaScript because 'unsafe-eval' #612

Comments

himulawang commented Jul 7, 2014

jmesserly commented Jul 7, 2014

himulawang commented Jul 8, 2014

jmesserly commented Jul 8, 2014

Dumbris commented Jul 11, 2014

Dumbris commented Jul 11, 2014

zoechi commented Jul 11, 2014

Dumbris commented Jul 11, 2014

prateekjassal commented Jul 29, 2014

robdodson commented Jul 29, 2014