Fix #269

h5bp · Sep 14, 2013 · 4bdd1ba · arthurvr · Feb 28, 2015 · alrra
1 parent 06d5f3e
commit 4bdd1ba
Show file tree

Hide file tree

Showing 9 changed files with 9 additions and 0 deletions.
diff --git a/posts/es6.md b/posts/es6.md
@@ -2,6 +2,7 @@ feature: ECMAScript 6
 status: avoid
 tags: es6
 kind: js
+moreurl: http://www.2ality.com/2013/07/es6-modules.html
 
 ECMAScript version 6 is the upcoming version of JavaScript that brings new features and heavy syntax changes. Currently only Chrome(17+) and Firefox support a highly experimental subset of ES6 features. 
 

diff --git a/posts/iframe-seamless.md b/posts/iframe-seamless.md
@@ -3,6 +3,7 @@ status: caution
 tags: none
 kind: html
 polyfillurls:
+moreurl: http://weblog.bocoup.com/third-party-javascript-development-future/#iframe-seamless
 
 This attribute instructs browsers to treat the iFrame's content more like inline markup than it would otherwise. Specifically, this means:
 

diff --git a/posts/iframe-srcdoc.md b/posts/iframe-srcdoc.md
@@ -3,6 +3,7 @@ status: use
 tags: polyfill
 kind: html
 polyfillurls:[srcdoc polyfill](https://github.com/jugglinmike/srcdoc-polyfill)
+moreurl: http://weblog.bocoup.com/third-party-javascript-development-future/#iframe-srcdoc
 
 This attribute allows for in-line specification of iframe content.
 

diff --git a/posts/input-search.md b/posts/input-search.md
@@ -2,6 +2,7 @@ feature: <input type=search>
 status: use
 tags: 
 kind: html
+moreurl: http://www.wufoo.com/html5/types/5-search.html
 
 A [search input](http://wufoo.com/html5/types/5-search.html) will fall back to a plain text input if it's not supported. The standard doesn't specify any behavior for this type, but recommends styling to match the platform's search fields (e.g. with rounded corners on OS X).  The style cancels out many CSS styles from being applied, and can be removed with `-webkit-appearance: none;`.  The recommendation here is to use `input[type=search]` to enhance your forms, so long as you're okay with the styling difference.
 

diff --git a/posts/microdata-domapi.md b/posts/microdata-domapi.md
@@ -3,6 +3,7 @@ status: use
 tags: polyfill ie6 gtie6
 kind: API
 polyfillurls: [microdata shim](https://github.com/termi/Microdata-JS)
+moreurl: http://dev.opera.com/articles/view/microdata-and-the-microdata-dom-api/
 
 Microdata is a new lightweight semantic meta-syntax. Using attributes, we can define nestable groups of name-value pairs of data, called microdata, which are generally based on the page's content. It gives us a whole new way to add extra semantic information and extend HTML5. Microdata is already being used by google to extract semantic meta data from your webpage.
 

diff --git a/posts/ol-reversed.md b/posts/ol-reversed.md
@@ -3,6 +3,7 @@ status: use
 tags: polyfill
 kind: html
 polyfillurls:[ol reversed polyfill](https://gist.github.com/1671548), [HTML5 reverse ordered lists](https://github.com/impressivewebs/HTML5-Reverse-Ordered-Lists)
+moreurl: http://html5doctor.com/ol-element-attributes/#reverse
 
 Please use the below polyfill, as WebKit is the only engine that supports it right now.
 Also see [Louis's ol[reversed] post](http://www.impressivewebs.com/reverse-ordered-lists-html5/).
diff --git a/posts/scoped-css.md b/posts/scoped-css.md
@@ -2,5 +2,6 @@ feature: style[scoped]
 status: avoid
 tags: 
 kind: css
+moreurl: http://css-tricks.com/saving-the-day-with-scoped-css/
 
 [Scoped stylesheets](http://css-tricks.com/saving-the-day-with-scoped-css/) are still in active development. Firefox 21 now includes this feature, but no other major browser currently supports it out-the-box.
diff --git a/posts/vibration.md b/posts/vibration.md
@@ -3,6 +3,7 @@ status: avoid
 tags: none
 kind: api
 polyfillurls:
+moreurl: https://developer.mozilla.org/en-US/docs/WebAPI/Vibration
 
 Vibration enables web apps access to a supporting device's force feedback motor.
 

diff --git a/posts/webcomponents.md b/posts/webcomponents.md
@@ -3,6 +3,7 @@ status: caution
 tags: polyfill
 kind: api
 polyfillurls: [Polymer](http://www.polymer-project.org/)
+moreurl: http://www.webcomponentsshift.com/
 
 The [Web Components](https://dvcs.w3.org/hg/webcomponents/raw-file/tip/explainer/index.html) API is a collection of four different specs from the W3C designed to work together: