31–40 of 127 posts
I wonder if Microsoft had said something remotely similar if WP had Windows like market share and sites were coded to IE!
At least WebKit/Blink are OpenSource and Microsoft can dream of being compatible easily.
Poor Windows Phone team. This is a symptom of the ecosystem's indifference to the windows phone platform. Browser vendors implementing hacks to trick web apps into presenting the right content because web developers have learned that they can't rely on the browser to render content properly. I think there's a lesson in here about treating your ecosystem right.
"In general, our advice is to develop a responsive site that can adapt to the capabilities of different devices. If you choose to build a mobile-specific experience then we recommend looking for the sub-string "mobile" in the user agent string to determine when to deliver mobile optimised content:" function isMobile() { return navigator.userAgent.toLowerCase().indexOf("mobile")>=0; } This is really the best we can do…
ug, that's already a bad check, but if they insist, why not just: /mobile/i.test(navigator.userAgent)
> The Mobile Web should just work for everyone I wonder if Microsoft had said something remotely similar if WP had Windows like market share and sites were coded to IE! At least WebKit/Blink are OpenSource and Microsoft can dream of being compatible easily.
> The Mobile Web should just work for everyone I wonder if Microsoft had said something remotely similar if WP had Windows like market share and sites were coded to IE! At least WebKit/Blink are OpenSource and Microsoft can dream of being compatible easily.
Microsoft invented user agent lying when MSIE 2.0 started advertising itself as Mozilla/1.22 (compatible; MSIE 2.0; Windows 95) , so we known exactly where that road goes.
Edit: The previous title was "Windows Phone's IE starts masquerading as mobile Safari to render pages properly" Looks like the webkit prefix tags are creating the new IE6. As usual, it's the web developers fault for not updating their CSS prefixes. http://css.dzone.com/articles/why-webkit-new-ie6-trap-vendor Mozilla, Opera and Microsoft have been complaining about this and Opera had already implemented support for th…
Isn't this basically the state of the User Agent strings across all browsers? The strings are a messy combination of different browsers, versions and rendering engines.
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Firefox/31.0
I wonder if we can just block IE11 on mobile. Not that many people use it anyway.
For comparison, can someone post the user agent strings from Safari iOS7 & Android Chrome?
WP 8.1: http://i.imgur.com/wxXof2J.png
FF OS: http://i.imgur.com/o8AZAYf.png
iOS Safari: http://i.imgur.com/uki6KQZ.png
Android Chrome: http://i.imgur.com/AJ6KNRa.png
