Merge branch 'master' into disable-upgrade

.github/CODEOWNERS

@@ -0,0 +1,2 @@
+# Code owners for Polymer
+* @sorvell @kevinpschaaf @TimvdLippe @azakus

.github/ISSUE_TEMPLATE.md

@@ -1,6 +1,6 @@
 <!--
 If you are asking a question rather than filing a bug, try one of these instead:
-- StackOverflow (http://stackoverflow.com/questions/tagged/polymer)
+- StackOverflow (https://stackoverflow.com/questions/tagged/polymer)
 - Polymer Slack Channel (https://bit.ly/polymerslack)
 - Mailing List (https://groups.google.com/forum/#!forum/polymer-dev)
 -->
@@ -9,8 +9,11 @@ If you are asking a question rather than filing a bug, try one of these instead:
 <!-- Example: Error thrown when calling `appendChild` on Polymer element -->
 
 #### Live Demo
-<!-- Fork this JSBin, or provide your own URL -->
-http://jsbin.com/luhaxab/1/edit
+<!-- jsBin starting point (fork and edit) -->
+https://jsbin.com/luhaxab/1/edit
+<!-- glitch.me starting point (remix and edit -- must be logged in to persist!) -->
+https://glitch.com/edit/#!/polymer-repro?path=my-element.html:2:0
+<!-- ...or provide your own repro URL -->
 
 #### Steps to Reproduce
 <!--

.travis.yml

@@ -12,9 +12,13 @@ before_script:
 - npm install -g bower gulp-cli@1
 - bower install
 - gulp lint-eslint
+- >-
+  npm run update-types && git diff --exit-code || (echo -e
+  '\n\033[31mERROR:\033[0m Typings are stale. Please run "npm run
+  update-types".' && false)
 script:
-- xvfb-run wct
-- if [ "${TRAVIS_PULL_REQUEST}" = "false" ]; then wct -s 'windows 10/microsoftedge@14' -s 'windows 10/microsoftedge@15' -s 'windows 8.1/internet explorer@11' -s 'os x 10.11/safari@9' -s 'macos 10.12/safari@10' -s 'macos 10.12/safari@11' -s 'Linux/chrome@41'; fi
+- wct -l chrome -l firefox
+- if [ "${TRAVIS_PULL_REQUEST}" = "false" ]; then travis_wait 30 ./util/travis-sauce-test.sh; fi
 env:
   global:
   - secure: bfF/o1ewpOxDNqTzWfvlwgRgGfP8OXhSQLLdEwZ6izO9tckMJuSNghk3qBXCEQJwTcUEyXP6EqfzIrRAvDXPa0H3OoinbrooDyV2wIDaVRK++WR2iZIqzqo3hGOdzm4tdrGJZe5av5Rk661Hls8aPfLbjdzcGuYXi8B4wZq2xMI=

CONTRIBUTING.md

@@ -42,7 +42,7 @@ If you find an issue, please do file it on the repository. The [Polymer/polymer
 
 For issues with elements the team maintains, please file directly on the element's repository. If you're not sure if a bug stems from the element or the library, air toward filing it on the element and we'll move the issue if necessary.
 
-Please file issues using the issue template provided, filling out as many fields as possible.  We love examples for addressing issues - issues with a Plunkr, jsFiddle, or jsBin will be much easier for us to work on quickly. You can start with [this jsbin](http://jsbin.com/luhaxab/edit) which sets up the basics to demonstrate a Polymer element.
+Please file issues using the issue template provided, filling out as many fields as possible. We love examples for addressing issues - issues with a jsBin, Plunkr, jsFiddle, or glitch.me repro will be much easier for us to work on quickly. You can start with [this jsbin](http://jsbin.com/luhaxab/edit) which sets up the basics to demonstrate a Polymer element.  If you need your repro to run in IE11, you can start from [this glitch](https://glitch.com/edit/#!/polymer-repro?path=my-element.html:2:0), which serves the source via polyserve for automatic transpilation, although you must sign up for a glitch.me account to ensure your code persists for more than 5 days (note the glitch.me _editing environment_ is not compatible with IE11, however the "live" view link of the running code should work).
 
 Occasionally we'll close issues if they appear stale or are too vague - please don't take this personally! Please feel free to re-open issues we've closed if there's something we've missed and they still need to be addressed.
 
@@ -90,15 +90,15 @@ To run the Polymer library unit tests:
 
 2.  Install the dependencies:
 
-        npm install && bower install
+		npm install && bower install
 
 3.  Run the tests:
 
-        npm test
+		npm test
 
     Or if you have `web-component-tester` installed locally:
 
-        wct
+		wct
 
 To run individual test suites:
 
@@ -110,45 +110,42 @@ Or:
 
 For example:
 
-    npm test test/unit/template.html
+	npm test test/unit/template.html
 
 You can also run tests in the browser:
 
-    polyserve
+	polyserve
 
 Navigate to:
 
 [`http://localhost:8080/components/polymer/test/runner.html`](http://localhost:8080/components/polymer/test/runner.html)
 
 ### Running Polymer element unit tests
 
-To run the element unit tests, you need a global 
-install of `web-component-tester` or `polyserve` (or both). 
+To run the element unit tests, you need a global install of `web-component-tester` or `polyserve` (or both).
 
-1.  Clone the element repo.
+1. Clone the element repo.
 
-2.  Install the dependencies.
+1. Install the dependencies.
 
-        bower install
+       bower install
 
-3.  Run the tests:
+1. Run the tests:
 
-	    wct
+       wct
 
-	Or run the tests in a browser:
+     Or run the tests in a browser:
 
-		polyserve
+       polyserve
 
-	Navigate to:
+     Navigate to:
 
-	<code>http://localhost:8080/components/<var>element-name</var>/test/runner.html</code>
+     <code>http://localhost:8080/components/<var>element-name</var>/test/runner.html</code>
 
 ### Configuring `web-component-tester`
 
 By default, `web-component-tester` runs tests on all installed browsers. You can configure it
 to run tests on a subset of available browsers, or to run tests remotely using Sauce Labs.
 
-See the [`web-component-tester` README](https://github.com/Polymer/web-component-tester) for 
-information on configuring the tool. 
-
-
+See the [`web-component-tester` README](https://github.com/Polymer/web-component-tester) for
+information on configuring the tool.

bower.json

@@ -21,7 +21,7 @@
   },
   "dependencies": {
     "shadycss": "webcomponents/shadycss#^v1.1.0",
-    "webcomponentsjs": "webcomponents/webcomponentsjs#^v1.0.19"
+    "webcomponentsjs": "webcomponents/webcomponentsjs#^v1.1.0"
   },
   "devDependencies": {
     "web-component-tester": "^6.0.0",