| 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: 1.0 | 4 Version: 1.0.3 |
| 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: |
| 11 This directory contains a copy of the following components which are a part of | 11 This directory contains a copy of the following components which are a part of |
| 12 the Polymer project: | 12 the Polymer project: |
| 13 -polymer core + externs | 13 -polymer core + externs |
| 14 -Iron elements and their dependencies | 14 -Iron elements and their dependencies |
| (...skipping 17 matching lines...) Expand all Loading... |
| 32 technologies called the Polymer. | 32 technologies called the Polymer. |
| 33 | 33 |
| 34 Local Modifications: | 34 Local Modifications: |
| 35 - Removed executable bit from the files in 'components/iron-selector'. | 35 - Removed executable bit from the files in 'components/iron-selector'. |
| 36 - Created a copy 'components-chromium' of the 'components' directory with the | 36 - Created a copy 'components-chromium' of the 'components' directory with the |
| 37 only difference that all inline JavaScript blocks are extracted from Polymer | 37 only difference that all inline JavaScript blocks are extracted from Polymer |
| 38 HTML elements to external JS files. This version of the Polymer is used in a web | 38 HTML elements to external JS files. This version of the Polymer is used in a web |
| 39 UI, where CSP forbids an execution of inline scripts. The extraction was made | 39 UI, where CSP forbids an execution of inline scripts. The extraction was made |
| 40 with the help of the Vulcanize tool (https://github.com/Polymer/vulcanize). | 40 with the help of the Vulcanize tool (https://github.com/Polymer/vulcanize). |
| 41 - Replaced CRLF line endings with LF line endings in text files. | 41 - Replaced CRLF line endings with LF line endings in text files. |
| 42 - Manually applied patch (https://github.com/Polymer/polymer/pull/1724/files) | |
| 43 to 'component-chromium/polymer/polymer-micro-extracted.js'. | |
| 44 | 42 |
| 45 To restore a content of the 'components', 'components-chromium' directorires | 43 To restore a content of the 'components', 'components-chromium' directorires |
| 46 from scratch, run ./reproduce.sh (requires bower and vulcanize >= 1.2). Then | 44 from scratch, run ./reproduce.sh (requires bower and vulcanize >= 1.2). |
| 47 download https://codereview.chromium.org/download/issue1165893005_40001.diff | |
| 48 and run 'git apply --reject issue1165893005_40001.diff'. | |
| 49 | 45 |
| 50 Note on Bower: | 46 Note on Bower: |
| 51 The directory can be updated by running "bower update". A new component can be | 47 The directory can be updated by running "bower update". A new component can be |
| 52 installed by running "bower install -S Polymer/<component>#version". Be sure to | 48 installed by running "bower install -S Polymer/<component>#version". Be sure to |
| 53 add the .bower.json file to the repository as it includes the revision | 49 add the .bower.json file to the repository as it includes the revision |
| 54 information of the polymer component. | 50 information of the polymer component. |
| 55 Also be sure that you listed all the added packages and **all their | 51 Also be sure that you listed all the added packages and **all their |
| 56 dependencies** in bower.json, and specified **exact** versions of every package | 52 dependencies** in bower.json, and specified **exact** versions of every package |
| 57 explicitly. That is needed because Bower can't handle recursive dependencies | 53 explicitly. That is needed because Bower can't handle recursive dependencies |
| 58 correctly (see http://stackoverflow.com/q/25899532). | 54 correctly (see http://stackoverflow.com/q/25899532). |
| OLD | NEW |