Merge pull request #3 from toolkitchen/master

update to latest toolkitchen

_includes/left-nav.html

@@ -20,7 +20,8 @@
       <li><a href="/platform/pointer-events.html">Pointer Events</a></li>
       <li class="divider"></li>
       <li class="nav-header">More information</li>
-      <li><a href="/tooling-strategy.html">Tools & Testing</a></li>
+      <li><a href="/tooling-strategy.html">Tools &amp; Testing</a></li>
+      <li><a href="/compatibility.html">Browser Compatibility</a></li>
       <li><a href="/changelog.html">Changelog</a></li>
     </ul>
   </div>

compatibility.md

@@ -0,0 +1,10 @@
+---
+layout: default
+title: Browser Compatibility
+---
+
+{{site.project_title}} and its polyfills are intended to work in the _latest
+version_ of "evergreen" browsers. The support matrix for each polyfill and their
+native browser implementation is below.
+
+<iframe src="https://docs.google.com/a/chromium.org/spreadsheet/pub?key=0Anye-JMjUkZZdDdoblh6dTlwcWRLQkhKbTVzdHJtcXc&single=true&gid=2&output=html&range=A1:Q43" seamless style="width:100%;height:830px;"></iframe>

css/site.css

@@ -25,6 +25,9 @@ code, pre {
   -o-user-select: none;
   user-select: none;
 }
+iframe[seamless] {
+  border: none;
+}
 figcaption {
   text-align: center;
   font-style: italic;

getting-the-code.md

@@ -3,11 +3,6 @@ layout: default
 title: Getting the Code
 ---
 
-<p class="alert">
-  <strong>Browser requirements</strong>: {{site.project_title}} will eventually support all major "evergreen"
-(auto-updating) browsers, it currently requires a WebKit-based browser such as Chrome or Safari.
-</p>
-
 ## Bring on the code!
 
 You can recursively clone and initialize all of its submodules with a single git command.

index.md

@@ -41,5 +41,5 @@ Toolkit platform shims the <a href="/platform/html-imports.html">HTML Imports</a
 All Toolkit components depend on `toolkit/toolkit.js` which provides the batteries
 or [sugaring layer](/toolkit-kernel-explainer.html). However, an application can
 only load `toolkit/platform/platform.js` directly to take advantage of the polyfill support.
-For examples of this, see the [CustomElementPlayground/](https://github.com/toolkitchen/projects/tree/master/CustomElementsPlayground) folder for examples.
+For examples of this, see the [CustomElementsPlayground](https://github.com/toolkitchen/projects/tree/stable/CustomElementsPlayground).
 

platform/pointer-events.md

@@ -1,6 +1,6 @@
 ---
 layout: default
-title: Abpout Pointer Events
+title: About Pointer Events
 subtitle: polyfill
 
 feature:

platform/shadow-dom.md

@@ -5,7 +5,7 @@ subtitle: polyfill
 
 feature:
   spec: https://dvcs.w3.org/hg/webcomponents/raw-file/tip/spec/shadow/index.html
-  status: <span class="label label-warning">in progress</span>
+  status: <span class="label label-success">functional</span>
   code: https://github.com/toolkitchen/ShadowDOM
   summary: "Shadow DOM is designed to provide encapsulation by hiding DOM subtrees under shadow
 roots. It provides a method of establishing and maintaining functional boundaries

samples/components/tk-binding-to-elements.html

@@ -17,7 +17,7 @@
       owner: "Eric",
       nameChanged: function() {
         if (this.name) {
-          // ensure capitilization
+          // ensure capitalization
           this.name = this.name[0].toUpperCase() +  this.name.slice(1);
         }
       }