| OLD | NEW |
|---|
| 1 Name: Polymer | 1 Name: Polymer |
| 2 Short Name: polymer | 2 Short Name: polymer |
| 3 URL: http://www.polymer-project.org | 3 URL: http://www.polymer-project.org |
| 4 Version: 0.3.5 | 4 Version: 0.3.5 |
| 5 Revision: (See components/<component>/.bower.json) | 5 Revision: (See components/<component>/.bower.json) |
| 6 License: BSD | 6 License: BSD |
| 7 License File: LICENSE.polymer | 7 License File: LICENSE.polymer |
| 8 Security Critical: no | 8 Security Critical: no |
| 9 | 9 |
| 10 Description: | 10 Description: |
| (...skipping 14 matching lines...) Expand all Loading... |
| 25 Polymer is comprised of two efforts: | 25 Polymer is comprised of two efforts: |
| 26 1. A set of core platform features (Shadow DOM, Custom Elements, MDV). | 26 1. A set of core platform features (Shadow DOM, Custom Elements, MDV). |
| 27 Initially, these core features will be enabled with a set of polyfills. As | 27 Initially, these core features will be enabled with a set of polyfills. As |
| 28 browsers begin to implement these new primitives, the polyfill platform layer | 28 browsers begin to implement these new primitives, the polyfill platform layer |
| 29 becomes smaller and better over time. | 29 becomes smaller and better over time. |
| 30 2. A next-generation web application framework built upon these core | 30 2. A next-generation web application framework built upon these core |
| 31 technologies called the Polymer. | 31 technologies called the Polymer. |
| 32 | 32 |
| 33 Local Modifications: | 33 Local Modifications: |
| 34 - Removed executable bit from the files in 'components/core-list'. | 34 - Removed executable bit from the files in 'components/core-list'. |
| 35 - Created a copy 'components-chromium' of the 'components' directory with the |
| 36 only difference that all inline JavaScript blocks are extracted from Polymer |
| 37 HTML elements to external JS files. This version of the Polymer is used in a web |
| 38 UI, where CSP forbids an execution of inline scripts. The extraction was made |
| 39 with the help of the Vulcanize tool (https://github.com/Polymer/vulcanize). |
| 35 | 40 |
| 36 To restore a content of the 'components' and '../third_party/web-animations-js' | 41 To restore a content of the 'components', 'components-chromium' directorires |
| 37 directory from scratch, run ./reproduce.sh (requires bower). | 42 from scratch, run ./reproduce.sh (requires bower and vulcanize). |
| 38 | 43 |
| 39 Note on Bower: | 44 Note on Bower: |
| 40 The directory can be updated by running "bower update". A new component can be | 45 The directory can be updated by running "bower update". A new component can be |
| 41 installed by running "bower install -S Polymer/<component>#version". Be sure to | 46 installed by running "bower install -S Polymer/<component>#version". Be sure to |
| 42 add the .bower.json file to the repository as it includes the revision | 47 add the .bower.json file to the repository as it includes the revision |
| 43 information of the polymer component. | 48 information of the polymer component. |
| 44 Also be sure that you listed all the added packages and **all their | 49 Also be sure that you listed all the added packages and **all their |
| 45 dependencies** in bower.json, and specified **exact** versions of every package | 50 dependencies** in bower.json, and specified **exact** versions of every package |
| 46 explicitly. That is needed because Bower can't handle recursive dependencies | 51 explicitly. That is needed because Bower can't handle recursive dependencies |
| 47 correctly (see http://stackoverflow.com/q/25899532). | 52 correctly (see http://stackoverflow.com/q/25899532). |
| 48 | |
| OLD | NEW |
|---|
Chromium Code Reviews
Issue 592593002:
Inline scripts were extracted from Polymer elements. (Closed)
Base URL: https://chromium.googlesource.com/chromium/src.git@master