3 out of 7 rated this helpful - Rate this topic

Differences Between the Desktop and Device WebBrowser Controls for Windows Phone

Windows Phone

March 22, 2012

The Windows Phone WebBrowser control is based on the Silverlight WebBrowser control, but with a few differences.


Silverlight

Windows Phone

Content loaded from the network has normal cross-site restrictions.

Content loaded from the network has the normal cross-site restrictions as well, but content loaded from isolated storage or by using the NavigateToString(String) method has no restrictions on cross-site access.

Does not have direct access to isolated storage.

Has direct access to isolated storage.

Designed to display HTML, but does not allow in-place navigation. For example, is it not possible to click a link to change the page displayed in the control.

Designed to display HTML and allows in-place navigation.

Includes HtmlBrush.

Does not include HtmlBrush.

Allows ActiveX controls.

Does not allow ActiveX controls.

InvokeScript is restricted to scripts loaded from the same site as the XAP package.

InvokeScript is not restricted to scripts loaded from the same site as the XAP package.

SaveToString() is restricted to scripts loaded from the same site as the XAP package.

SaveToString() is not restricted to scripts loaded from the same site as the XAP package.

The WebBrowser control is specified by using the <WebBrowser> tag.

The WebBrowser control is specified by using the <WebBrowser> tag and must contain an xmlns prefix.

Cookies must be shared between the application and the WebBrowser control.

Cookies are shared by the application and the WebBrowser control.

Did you find this helpful?
(1500 characters remaining)