Merge pull request #197 from jeffreybarke/patch-1

Removed recommendation to use the geolocation shim polyfill. As far as I...
h5bp · Jul 12, 2012 · 6fb32d5 · 6fb32d5
2 parents 35d50c4 + bd49c98
commit 6fb32d5
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/posts/geolocation.md b/posts/geolocation.md
@@ -2,6 +2,6 @@ feature: geolocation
 status: use
 tags: fallback gtie8
 kind: api 
-polyfillurls: [geolocation shim](https://gist.github.com/366184), [geo-location-javascript](http://code.google.com/p/geo-location-javascript/)
+polyfillurls: [geo-location-javascript](http://code.google.com/p/geo-location-javascript/)
 
-[geolocation shim](https://gist.github.com/366184) uses Google's IP-GeoCoding service as a fallback. [geo-location-javascript](http://code.google.com/p/geo-location-javascript/) doesn't but has hooks into BlackBerry, WebOS, and Google Gears specific APIs. In most cases, you should just not expose Geo features in your app if the feature is not natively present.
+[geo-location-javascript](http://code.google.com/p/geo-location-javascript/) has hooks into BlackBerry, WebOS, and Google Gears specific APIs. In most cases, you should just not expose Geo features in your app if the feature is not natively present.