Jul 14, 2010 at 3:46 PM
Edited Jul 14, 2010 at 3:47 PM
The new release which is scheduled for the 27th July is to contain the following major change; I’d like to share this with you in advance.
Our goal with this change is to ensure that existing sites can be updated to support mobile content. As such we feel it is important to ensure that any .browser file placed
on the site should not break the existing PC experience. We are therefore planning on introducing the IsMobileDevice Guard:
Our .browser assumes that it is running on top of the default ASP.NET configuration files. The .browser applies its capabilities irrespective of the incoming device. For instance,
when the .browser sees a PC based user agent string the .browser will still set capabilities such as “CanInitiateVoiceCalls” based on the default assumptions we have for mobile devices. This can cause issues on sites which host both PC and mobile
content. To resolve these issues we will ensure that MDBF capabilities are only set when we believe that the UA string is a mobile UA. This essentially uses an “if” statement as follows:
IF ( UA string comes from a mobile device ) THEN
IsMobile = true
//Apply shim settings
IsMobile = false
//Do nothing – do not apply shim settings
This should ensure that the mobile capabilities are never applied when a PC browser visits a site
Note: We planned to apply this change in April, but it was postponed until now.