I guess that you came across the issue related with template generation mechanism, which is integral part of every Kendo UI widget.
Due to performance consideration Kendo template are building string representation of the output which is later eval-ed/via new Function
/. Unfortunately in Chrome extensions such behavior is not allowed by default. Similar approach is also used by other js template engines.
There is a bug report which lists other js frameworks that have same issue: http://code.google.com/p/chromium/issues/detail?id=107538#c35
Currently the only solution(which we were able to find so far) is to use the following manifest configuration.
"Chrome extension using Kendo UI"
...other config settings
"default-src 'self' 'unsafe-inline' 'unsafe-eval' kendo.min.all.js"
Imported parts of the configuration:
- "content_security_policy": "default-src 'self' 'unsafe-inline' 'unsafe-eval' kendo.min.all.js"
- this allows evals (i.e new Function("function body")
) generation for kendo.min.all.js file.
- "manifest_version": 1
- the version of the manifest json must be 1, otherwise the above content security policy will not be accepted.
I hope this explains the current state of affairs.
the Telerik team
Join us on our journey to create the world's most complete HTML 5 UI Framework - download Kendo UI