PRB: Style and Font Properties Set on a Mobile Control May Not Appear in HTML Browsers

If you set certain style or font properties on a mobile control, they may not appear when you browse with a Hypertext Markup Language (HTML) browser that supports the style or font.

This behavior can occur because style and font properties are not rendered to an HTML browser as a Cascading Style Sheet (CSS), but are rendered with non-CSS properties. Style and font properties are not rendered by a mobile control if the control cannot be rendered with non-CSS properties to represent the style or font.

For example, a mobile Command control with the BackColor property set to any color, renders a HTML <INPUT> tag to the browser. The HTML <INPUT> tag has a type=button attribute, but doesn't have an attribute to represent the background color. This is because the HTML <INPUT> tag does not have a non-CSS representation for setting the background color.

This behavior occurs with other mobile controls in the Microsoft Mobile Internet Toolkit (MMIT).

NOTE: The Mobile Designer that was used to develop MMIT Web applications in Visual Studio .NET does not disable style and font properties that have the behavior that is described in this article.

To resolve this behavior, leave the style and font properties available so that you can extend the MMIT to support CSS. MMIT is built upon a device adapter model that allows you to change the rendering logic of a mobile control. You can change the rendering logic of a mobile control if you modify the Devise Adapter files that are included with the MMIT.

This behavior is by design.

The MSDN documentation included with MMIT contains additional information on modifying MMIT Device Adapter files.