Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Chrome Packaged App: including UI elements in an application will show some errors #249

Closed
dinhvh opened this issue Aug 21, 2013 · 4 comments

Comments

@dinhvh
Copy link

dinhvh commented Aug 21, 2013

I created the following Chrome Packaged App:
https://github.com/dinhviethoa/polymer-simple
it's implementing the ui toolbar example in a Chrome Packaged App.

I had the following error in the javascript console:

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.
 deprecated.js:12
Uncaught InvalidCharacterError: Failed to call 'register' on 'Document' for type 'polymer-element': : 'polymer-element' is not a valid name. deprecated.js:12
Uncaught TypeError: Property 'Polymer' of object [object Object] is not a function build.js:29
@dinhvh
Copy link
Author

dinhvh commented Aug 21, 2013

It's probably blocked by https://codereview.chromium.org/23292002/

@dinhvh
Copy link
Author

dinhvh commented Aug 21, 2013

The consequence of those issues is that I can't see the polymer elements with their CSS styling and behavior.

@dfreedm
Copy link
Member

dfreedm commented Aug 21, 2013

Yep, it seems like that rev still needs to hit Chrome first.

@dfreedm
Copy link
Member

dfreedm commented Aug 22, 2013

Should be fixed in today's Canary build 218872.

@dinhvh dinhvh closed this as completed Aug 22, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants