| OLD | NEW |
|---|
| (Empty) |
| 1 Name: Polymer | |
| 2 Short Name: polymer | |
| 3 URL: http://www.polymer-project.org | |
| 4 Version: 1.2.1 | |
| 5 Revision: (See components/<component>/.bower.json) | |
| 6 License: BSD | |
| 7 License File: ../LICENSE.polymer | |
| 8 Security Critical: no | |
| 9 | |
| 10 Description: | |
| 11 This directory contains a copy of the following components which are a part of | |
| 12 the Polymer project: | |
| 13 -polymer core + externs | |
| 14 -Iron elements and their dependencies | |
| 15 -Paper elements and their dependencies | |
| 16 See bower.json for a full list of components. | |
| 17 | |
| 18 The version can be found in header of polymer/polymer.js. The license can | |
| 19 be found in polymer/LICENSE. | |
| 20 | |
| 21 The source git repositories can be found at: | |
| 22 Core Library - https://github.com/Polymer/polymer | |
| 23 Elements - https://github.com/PolymerElements/<element name> | |
| 24 | |
| 25 Polymer is comprised of two efforts: | |
| 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 | |
| 28 browsers begin to implement these new primitives, the polyfill platform layer | |
| 29 becomes smaller and better over time. | |
| 30 2. A next-generation web application framework built upon these core | |
| 31 technologies called the Polymer. | |
| 32 | |
| 33 Local Modifications: | |
| 34 - Removed executable bit from the files in 'components/iron-selector'. | |
| 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 using Crisper (https://github.com/PolymerLabs/crisper). | |
| 40 - Replaced CRLF line endings with LF line endings in text files. | |
| 41 - Apply chromium.patch with local modifications. The patch is applied to | |
| 42 components-chromium (i.e. after extracting the inline scripts) so that the | |
| 43 results of 'git diff' (after any new local changes are applied) can be appended | |
| 44 to chromium.patch. | |
| 45 | |
| 46 To restore the contents of the 'components' and 'components-chromium' | |
| 47 directories from scratch, run ./reproduce.sh (requires bower and crisper). | |
| 48 | |
| 49 Note on Bower: | |
| 50 The directory can be updated by running "bower update". A new component can be | |
| 51 installed by running "bower install -S Polymer/<component>#version". Be sure to | |
| 52 add the .bower.json file to the repository as it includes the revision | |
| 53 information of the polymer component. | |
| 54 Also be sure that you listed all the added packages and **all their | |
| 55 dependencies** in bower.json, and specified **exact** versions of every package | |
| 56 explicitly. That is needed because Bower can't handle recursive dependencies | |
| 57 correctly (see http://stackoverflow.com/q/25899532). | |
| OLD | NEW |
|---|
Chromium Code Reviews
Issue 1623693002:
Tidy up in Polymer directory. (Closed)
Base URL: https://chromium.googlesource.com/chromium/src.git@master