Microsoft preps web sites for new Windows Phone 7 IE

As we get closer to the release of the Mango update for Windows Phone 7, website operators will have to make some adjustments in order to accommodate the new version of Internet Explorer 9 that will be included in the update. In the latest Windows Phone 7 developer blog entry, Microsoft's Charles Morris gives those website operators details on the new user-agent string for the mobile version of IE9. Those changes let websites detect when a Windows Phone 7 Mango user is accessing the site with the new version of the browser.

As you might expect this blog entry is a bit on the technical side. Morris describes how the user-string for the new mobile version of IE9 works, saying, "In fact, we can reuse most of the description from the original post announcing the IE9 UA string on Windows." For those of you who run websites, Morris posts what the UA string should be to properly support WP7.

Morris says that while having user-agent features is a good way to identify which browser is accessing your site, he adds that site operators should " ... use feature and behavior detection to detect specific browsers wherever possible." He also says, "If you do decide to use UA detection, we suggest using the 'IEMobile' token to identify Internet Explorer on Windows Phone as a mobile browser." Finally he says that now would be a good time to put in some extra features such as HTML5 video that can be detected on the new mobile version of iE9.

Report a problem with article
Previous Story

Nook eReader selling well, says Barnes and Noble

Next Story

HP gives more info about TouchPad business

11 Comments

Commenting is disabled on this article.

Why do they mix it up with IE, just create a webkit browser ? Or allow people to add browsers with their own engine in WP7 ? That's one of the little things I don't like about WP7 when the rest of the OS is great.

I really don't care about html5 at the moment.

Gaffney said,
Why do they mix it up with IE, just create a webkit browser ? Or allow people to add browsers with their own engine in WP7 ? That's one of the little things I don't like about WP7 when the rest of the OS is great.

I really don't care about html5 at the moment.

If they use webkit, there are people in the open source community that would'nt trust the code. The may claim that the code has some hidden traps in it, i.g they are patented by Microsoft, or that the code is non complient etc.

As to the us thier own engine thing. You can.
Provided that you write it in a .net complient lcoding language first. When you start runing code on bear metal, you start losing control of your platform.

Stewart Gilligan Griffin said,
think your user agent string is messed up in that quote

The editor was mangling it because of all of the special characters...

That dosent change the fact that EVERYONE will still detect IE, and feed it IE6 code thus screwing it up anyway. Same thing with the mobile stuff, they see mobile and give it a text page, instead of the normal mobile or iphone page.

flexkeyboard said,
Oh look, another sheep. Bah eheheheheh. Follow it!

What is sheepish about this? I have a windows phone (HD7), and a Touch Pro 2 before that, and sites have a bad habit of detecting thier browsers badly. The gawker websites DEFAULT to the mobile view even when you set the ua as dektop, the Engadget website omits parts of the page even though it works without flaws on the hd7, I don't know what is up with the Newin mobile version, but the writing anything in the comments box is a task because of the slow down.

As a user of said browser, I have legitimate concerns, and seeing what the habits of web 'developers' have been, I am highly skeptical that they will take heed of these changes and act acordingly.

This is a test of the neowin comment box on the Mango RC on an HTC Surround, I am typing at full speed and I am no experiencing the slowdown I had typing here under NoDo. One issue that exists though is that the text box would not show your whole quote, nor let me scroll down. Another issue is that the mobile theme does not seem to use -border-radius in CSS, rather it seems to use -webkit-border-radius