Geo URI scheme

[Fyrd]

geo: url support - http://tools.ietf.org/html/draft-mayrhofer-geo-uri-00

---

This issue was imported from Google Moderator

Moderator votes: +7
Issue added by wskid on 2012-01-16

[lcichanowicz]

+1

[Schweinepriester]

+1

[jtakalai]

+1

[Shabablinchikow]

+1

[oliverseal]

+1

[beeryt]

+1

[renaatdemuynck]

+1

[jameswilson]

Copying my investigation/info from #5268

Would be useful to know which platforms/devices support links in the Geo URI scheme, eg:

<a href="geo:12.345,67.890?z=17">geo:12.345,67.890?z=17</a> 

"Support" in this case, would be defined as actually sending the user to a maps program, or a map website (eg google, or openstreetmaps).

Note: there is an existing custom protocol handling in caniuse, but it doesn't mention all of the safelisted schemes, such as "tel" or "geo", so a search query or short turns up nothing.

Examples

https://caniuse.com/#search=tel
https://caniuse.com/#search=telelphone <-- turns up only <input type="telephone">
https://caniuse.com/#search=geouri

Resources

https://en.wikipedia.org/wiki/Geo_URI_scheme
https://html.spec.whatwg.org/multipage/system-state.html#custom-handlers
https://caniuse.com/#feat=registerprotocolhandler

[randomRooster]

This would be very helpful to have available.
As far as I'm aware, there is no way how to cleanly do feature detection for Geo URI support without relying on user agent sniffing. For now I'm naively polyfilling if the user agent reports an Apple Device (the best way seems to be map links). Everything that's not Safari seems to handle Geo URI nicely.
It would be nice to have a more precise way to determine if a polyfill is required.