-
CORS, or cross-origin resource sharing, enables a few things, but most notably cross-domain AJAX. IE8 introduced XDomainRequest.aspx), so really only IE7 needs help with cross-domain files. Consider the polyfills below or you can fallback to using a simple proxy.
+
CORS, or cross-origin resource sharing, enables a few things, but most notably cross-domain AJAX. IE8 introduced XDomainRequest, so really only IE7 needs help with cross-domain files. Consider the polyfills below or you can fallback to using a simple proxy.
@@ -1587,7 +1587,9 @@
websockets
Making your app real-time is a huge boost and Socket.io 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.
-
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.
+
web-socket-js is a natural polyfill for the Javascript WebSocket API transferring data through Flash Sockets when WebSockets aren't available.
+
+
As a word of caution, the protocol backing the Web Socket API has become an IETF standard, but Safari has not yet implemented the new version. It is recommended forcing Flash on Safari (or disabling WebSockets on Safari) for now.
@@ -1611,7 +1613,7 @@
WebSQL DB
-
Although it initially found favor as a clientside database API, it has now been abandoned in favor of IndexedDB. We therefor recommend that you do not use WebSQL.
+
Although it initially found favor as a clientside database API, it has now been abandoned in favor of IndexedDB. We therefore recommend that you do not use WebSQL.
diff --git a/posts/fontface.md b/posts/fontface.md
index f6643c18..df80903b 100644
--- a/posts/fontface.md
+++ b/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.
diff --git a/posts/placeholder.md b/posts/input-placeholder.md
similarity index 50%
rename from posts/placeholder.md
rename to posts/input-placeholder.md
index a7224129..b27b50ce 100644
--- a/posts/placeholder.md
+++ b/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.
\ No newline at end of file