Open GoogleCodeExporter opened 9 years ago
IE9 simply doesn't seem to have any support for geo location for javascript.
Have you seen that working in other places?
Original comment by whoiss...@gmail.com
on 19 May 2011 at 4:23
docs: http://msdn.microsoft.com/en-us/library/gg589519(v=vs.85).aspx
example: http://ie.microsoft.com/testdrive/HTML5/Geolocation/Default.html
Original comment by bensamg...@gmail.com
on 20 May 2011 at 7:28
Granted Microsoft's database of wi-fi networks is not nearly as good as
Google's or Apple's. For me they are several miles off whereas google/apple are
spot on.
Original comment by bensamg...@gmail.com
on 20 May 2011 at 7:31
hi, i don't have windows and IE9 myself, but their example code looks exactly
like what geo.js does. Does their example work for you, but not the geo.js
library? Did you spot a difference?
Thank you,
Stan
else if (typeof(navigator.geolocation)!=u)
{
provider=navigator.geolocation;
pub.getCurrentPosition = function(success, error, opts)
{
function _success(p)
{
//for mozilla geode,it returns the coordinates slightly differently
if(typeof(p.latitude)!=u)
{
success({timestamp:p.timestamp, coords: {latitude:p.latitude,longitude:p.longitude}});
}
else
{
success(p);
}
}
provider.getCurrentPosition(_success,error,opts);
}
}
Original comment by whoiss...@gmail.com
on 23 May 2011 at 11:29
yes their example works fine in IE but when I run your sample.html it returns
"Functionality not available". Am not very good at javascript..
Original comment by bensamg...@gmail.com
on 23 May 2011 at 12:51
It works fine for me on IE9 for the pc but not in IE9 for Windows Phone 7.
Running the sample.html returns "Functionality not available"
Original comment by anatoly....@gmail.com
on 10 Aug 2011 at 8:54
You need to add the same doctype to your HTML. Try this beginning snippet of
HTML:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type" />
Original comment by pkgi...@gmail.com
on 25 Aug 2011 at 4:05
So I need to update the sample files to reflect this
Original comment by whoiss...@gmail.com
on 25 Aug 2011 at 10:01
Original issue reported on code.google.com by
bensamg...@gmail.com
on 18 May 2011 at 8:13