Hi Thomas,

The mobile view is determined by the user agent string which is intended only to detect smart phones. For tablets I recommend people to use responsive design techniques to make the main skin work well but for the small screens of phones a separate skin should be used to make optimization easier and to make the mobile skin lighter by leaving out css that is only for the main skin.

It does not depend on Mobile Kit Pro though it has a special menu control that is optimized for phones, the SiteMenu and PageMenu included in mojoPortal should filter out webonly content when the user agent detected is a phone.

However in looking into it I found that in the case where we are using the new FlexMenu control inside SiteMenu and PageMenu it was not setting the IsMobileSkin property on the FlexMenu therefore the FlexMenu was not filtering the content as it should for mobile. So there was a bug in this case. It is now fixed in the source code repository. FlexMenu is used now by default in most skins we ship and in Artisteer 4.1 skins exported with our latest plugin, you will see UseFlexMenu="true" on <portal:SiteMenu and <portal:PageMenu if it is used.

For those who cannot update from the source code, a workaround is possible by setting a theme.skin setting in the skin for mobile if using FlexMenu like this:

<portal:FlexMenu runat="server" SkinID="SiteMenu"
    IsMobileSkin="true"
...

/>

<portal:FlexMenu runat="server" SkinID="PageMenu"
    IsMobileSkin="true"
...
/>

But this should only be done if using a different skin for mobile, ie you would not want those settings in the non mobile skin.

Thanks,

Joe