Roll Polymer to 1.3.1

third_party/polymer/v1_0/components-chromium/iron-list/README.md

 
 <!---
 
 This README is automatically generated from the comments in these files:
 iron-list.html
 
 Edit those files, and our readme bot will duplicate them over here!
 Edit this file, and the bot will squash your changes :)
 
 The bot does some handling of markdown. Please file a bug if it does the wrong
 thing! https://github.com/PolymerLabs/tedium/issues
 
 -->
 
-[![Build Status](https://travis-ci.org/PolymerElements/iron-list.svg?branch=master)](https://travis-ci.org/PolymerElements/iron-list)
+[![Build status](https://travis-ci.org/PolymerElements/iron-list.svg?branch=master)](https://travis-ci.org/PolymerElements/iron-list)
 
-_[Demo and API Docs](https://elements.polymer-project.org/elements/iron-list)_
+_[Demo and API docs](https://elements.polymer-project.org/elements/iron-list)_
 
 
 ##&lt;iron-list&gt;
 
 `iron-list` displays a virtual, 'infinite' list. The template inside
 the iron-list element represents the DOM to create for each list item.
 The `items` property specifies an array of list item data.
 
 For performance reasons, not every item in the list is rendered at once;
 instead a small subset of actual template elements *(enough to fill the viewport)*
@@ skipping 102 matching lines @@
 visible on the screen. e.g. the page has 500 nodes, but only 20 are visible at the time.
 This is why we refer to it as a `virtual` list. In this case, a `dom-repeat` will still
 create 500 nodes which could slow down the web app, but `iron-list` will only create 20.
 
 However, having an `iron-list` does not mean that you can load all the data at once.
 Say, you have a million records in the database, you want to split the data into pages
 so you can bring a page at the time. The page could contain 500 items, and iron-list
 will only render 20.