Tidy up in Polymer directory.

third_party/polymer/README.chromium

Index: third_party/polymer/README.chromium
diff --git a/third_party/polymer/README.chromium b/third_party/polymer/README.chromium
index a873957093a9838323dcc5328d6eca5258273e47..884dd07c84c27f98f3128fe3a9fa771e0aa444dd 100644
--- a/third_party/polymer/README.chromium
+++ b/third_party/polymer/README.chromium
@@ -1,26 +1,20 @@
 Name: Polymer
 Short Name: polymer
 URL: http://www.polymer-project.org
-Version: 0.5.2-4
-Revision: (See components/<component>/.bower.json)
+Version: 1.2.3
+Revision: (see v1_0/components_summary.txt)
 License: BSD
 License File: LICENSE.polymer
 Security Critical: no
 
 Description:
-This directory contains a copy of the following components which are a part of
-the Polymer project:
--polymer
--all core elements and their dependencies (except "core-docs",
- "core-component-page", and "core-doc-viewer")
--all paper elements and their dependencies (except "paper-menu-button")
-See bower.json for a full list of components.
-
-The version can be found in header of polymer/polymer.js. The license can
-be found in polymer/LICENSE.
+This directory contains a copy of the Polymer framework and some elements from
+the Polymer elements catalog (https://elements.polymer-project.org/). See
+v1_0/components_summary.txt for a full list of components.
 
 The source git repositories can be found at:
-https://github.com/Polymer/<component>
+https://github.com/Polymer/polymer
+https://github.com/PolymerElements/<component-name>

[michaelpg, 2016/01/23 04:28:15]

+PolymerLabs for polymer-externs

[dzhioev (left Google), 2016/01/25 23:31:35]

Done.

 
 Polymer is comprised of two efforts:
 1. A set of core platform features (Shadow DOM, Custom Elements, MDV).
@@ -31,23 +25,21 @@ becomes smaller and better over time.
 technologies called the Polymer.
 
 Local Modifications:
-- Removed executable bit from the files in 'components/core-list'.
-- Created a copy 'components-chromium' of the 'components' directory with the
-only difference that all inline JavaScript blocks are extracted from Polymer
-HTML elements to external JS files. This version of the Polymer is used in a web
-UI, where CSP forbids an execution of inline scripts. The extraction was made
-with the help of the Vulcanize tool (https://github.com/Polymer/vulcanize).
+- Applied modifications that can be found in v1_0/chromium.patch.
+- All inline JavaScript blocks are extracted from Polymer HTML elements to
+external JS files. This version of the Polymer is used in a web UI, where CSP
+forbids an execution of inline scripts. The extraction was made with the help of
+the Crisper tool (https://github.com/PolymerLabs/crisper).
+- Removed executable bit from some files.
+- Resolved encoding issues.
 - Replaced CRLF line endings with LF line endings in text files.
 
-To restore a content of the 'components', 'components-chromium' directorires
-from scratch, run ./reproduce.sh (requires bower and vulcanize >= 0.7.2).
+To restore a content of the 'components-chromium' directory from scratch, run
+./v1_0/reproduce.sh (requires bower and crisper) on a Linux machine.
 
 Note on Bower:
 The directory can be updated by running "bower update". A new component can be
-installed by running "bower install -S Polymer/<component>#version". Be sure to
-add the .bower.json file to the repository as it includes the revision
-information of the polymer component.
-Also be sure that you listed all the added packages and **all their
-dependencies** in bower.json, and specified **exact** versions of every package
-explicitly. That is needed because Bower can't handle recursive dependencies
-correctly (see http://stackoverflow.com/q/25899532).
+installed by running "bower install -S PolymerElements/<component>#version".
+Be sure to add the .bower.json file to the repository as it includes the
+revision information of the polymer component.
+Also be sure that you listed all the added packages in bower.json.