11–20 of 87 posts
> Internet Explorer 10 for Windows Phone 8 uses the same rendering engine as the desktop build of Internet Explorer 10, which is certainly capable of loading and running Google Maps. This argument makes no sense. Google Maps desktop works on IE10, but Google Maps mobile is clearly a totally different site. I think people are jumping to conclusions here.
Did you really just type that?
Its a pretty huge oversight by MS given that WebKit, Firefox and Opera do it just fine.
This argument is ridiculous. What business sense would there be for Google to restrict access to Maps on one platform in the interest of "competition"? It's not like any potential WP8 users will be swayed over to Android just because of GMaps, considering Bing Maps is a more than adequate alternative. Occam's razor: it's more than likely that they just don't want to invest the dev + support time to support WP8 (web o…
> Internet Explorer 10 for Windows Phone 8 uses the same rendering engine as the desktop build of Internet Explorer 10, which is certainly capable of loading and running Google Maps. This argument makes no sense. Google Maps desktop works on IE10, but Google Maps mobile is clearly a totally different site. I think people are jumping to conclusions here.
>a totally different site. Did you really just type that?
The Windows Phone browser does not send touchstart or touchmove events. This alone makes it damn near impossible left to implement decent maps, so the claims that its the equivalent of IE10 is incorrect. Its a pretty huge oversight by MS given that WebKit, Firefox and Opera do it just fine.
It's not shenanigans, it's browser sniffing instead of feature detection, and Google does it on too many of its sites. What's annoying about this "controversy" is that the minuscule marketshare slice that is windows phones merits this much coverage, when this is daily life for the significantly larger (in absolute number) set of Opera users, on desktop and mobile. There's also a very real reason that Mozilla has cons…
Maps on Opera, Nexus 4: http://i.imgur.com/0DXVz.png
You were saying?
The real problem is that it is a slap in the face for html. What does Google think it is? Is it a presentation layer standard with ideally many implementations or is it a file format for web kit?
This argument is ridiculous. What business sense would there be for Google to restrict access to Maps on one platform in the interest of "competition"? It's not like any potential WP8 users will be swayed over to Android just because of GMaps, considering Bing Maps is a more than adequate alternative. Occam's razor: it's more than likely that they just don't want to invest the dev + support time to support WP8 (web o…
Earlier quoted context omitted.
>a totally different site. Did you really just type that?
Why not? It's obviously not the same codebase as the desktop version of the site, why would you expect because the desktop version of the site supports IE10 that the mobile version of the site would as well?
The Windows Phone browser does not send touchstart or touchmove events. This alone makes it damn near impossible left to implement decent maps, so the claims that its the equivalent of IE10 is incorrect. Its a pretty huge oversight by MS given that WebKit, Firefox and Opera do it just fine.
