placeholder text update

index.html

@@ -292,7 +292,7 @@ <h2 class="name">CORS </h2>
             </header>
             <div class="more">
               <div class="recco">
-                <p>CORS, or cross-origin resource sharing, enables a few things, but most notably cross-domain AJAX. IE8 introduced <a href="http://msdn.microsoft.com/en-us/library/ie/cc288060(v=vs.85">XDomainRequest</a>.aspx), so really only IE7 needs help with cross-domain files. Consider the polyfills below or you can fallback to using a <a href="http://benalman.com/projects/php-simple-proxy/">simple proxy</a>.</p>
+                <p>CORS, or cross-origin resource sharing, enables a few things, but most notably cross-domain AJAX. IE8 introduced <a href="http://msdn.microsoft.com/en-us/library/ie/cc288060(v=vs.85).aspx">XDomainRequest</a>, so really only IE7 needs help with cross-domain files. Consider the polyfills below or you can fallback to using a <a href="http://benalman.com/projects/php-simple-proxy/">simple proxy</a>.</p>
               </div>
               <div class="polyfills"><b>Recommended polyfills: </b><p><a href="https://github.com/toolness/postmessage-proxied-xhr/#readme">postmessage-proxied-xhr</a>, <a href="http://flxhr.flensed.com/">flXHR</a> (requires crossdomain.xml), <a href="https://github.com/eligrey/pmxdr">pmxdr</a> (requires host installed)</p></div> 
 
@@ -1587,7 +1587,9 @@ <h2 class="name">websockets </h2>
               <div class="recco">
                 <p>Making your app real-time is a huge boost and <a href="http://socket.io/">Socket.io</a> is a Node+Javascript framework that helps with downlevel transports for browsers lacking native websocket support (and supports IE6+). However be prepared to tune your AJAX polling or Comet in order to meet the needs of your app.</p>
 
-<p>As a word of caution, the protocol backing the Web Socket API has changed several times in the past year, but has matured enough to not introduce any more breaking changes.</p>
+<p><a href="https://github.com/gimite/web-socket-js">web-socket-js</a> is a natural polyfill for the Javascript WebSocket API transferring data through Flash Sockets when WebSockets aren't available.</p>
+
+<p>As a word of caution, the protocol backing the Web Socket API has become an <a href="http://tools.ietf.org/html/rfc6455">IETF standard</a>, but Safari has not yet implemented the new version.  It is recommended forcing Flash on Safari (or disabling WebSockets on Safari) for now.</p>
               </div>
               <div class="polyfills"><b>Recommended polyfills: </b><p><a href="http://socket.io/">Socket.io</a>, <a href="https://github.com/gimite/web-socket-js">web-socket-js</a></p></div> 
 
@@ -1611,7 +1613,7 @@ <h2 class="name">WebSQL DB </h2>
             </header>
             <div class="more">
               <div class="recco">
-                <p>Although it initially found favor as a clientside database API, it has now <a href="http://www.w3.org/TR/webdatabase/#status-of-this-document">been abandoned</a> in favor of IndexedDB. We therefor recommend that you do not use WebSQL. </p>
+                <p>Although it initially found favor as a clientside database API, it has now <a href="http://www.w3.org/TR/webdatabase/#status-of-this-document">been abandoned</a> in favor of IndexedDB. We therefore recommend that you do not use WebSQL. </p>
               </div>
               <div class="polyfills"></div> 
 

posts/fontface.md

@@ -4,6 +4,6 @@ tags: fallback
 kind: css
 polyfillurls:
 
-Use the [Font Squirrel Generator](http://www.fontsquirrel.com/fontface/generator) for fonts you have license for using as web fonts. [Font Squirrel @font-face syntax](http://www.fontspring.com/blog/the-new-bulletproof-font-face-syntax) is also the most bullet-proof way of serving web fonts. You do not need polyfills - just fonts in several formats; WOFF is preferred, followed by TTF and then EOT. 
+Use the [Font Squirrel Generator](http://www.fontsquirrel.com/fontface/generator) for fonts you have license for using as web fonts. [Fontspring @font-face syntax](http://www.fontspring.com/blog/the-new-bulletproof-font-face-syntax) is also the most bullet-proof way of serving web fonts. You do not need polyfills - just fonts in several formats; WOFF is preferred, followed by TTF and then EOT. 
 
 Also, don't use sIFR or Cufon anymore.

posts/placeholder.md → posts/input-placeholder.md

@@ -1,7 +1,9 @@
-feature: placeholder
+feature: input[placeholder]
 status: use
 tags: gtie9
 kind: html
 polyfillurls:[Placeholder jQuery Plugin](https://github.com/mathiasbynens/jquery-placeholder)
 
 Input placeholders are simply ignored in IE 9 and below. Note that they are only applied when the **type** of the input is *text*, *search*, *tel*, *url*, or *email*. Otherwise, it is ignored.
+
+`input[placeholder]` is commonly the first polyfill anyone writes and, as such, there are [many of them](http://bit.ly/polyfills). Password inputs and submit event clearing are among many of the gotchas that catch naïve implemenations; Mathias's polyfill below handles these cases very well.