HTML and DOM API changes list (HTML)
[ This article is for Windows 8.x and Windows Phone 8.x developers writing Windows Runtime apps. If you’re developing for Windows 10, see the latest documentation ]
Windows Runtime apps using JavaScript use Windows Internet Explorer Standards mode when processing most of their HTML and JavaScript, but there are some HTML and DOM APIs that work differently or aren't supported. Here's the list of the HTML and DOM APIs that behave differently or aren't supported for Windows Runtime apps using JavaScript.
When writing code for web sites and Windows apps using JavaScript, you can use feature detection to determine whether an API is supported before you use it. For more info, see Same Markup: Writing Cross-Browser Code.
API | Description |
---|---|
Behavior change. Cannot be used to open a new window inside the app. If you try to open an external web page in a new window (such as by setting target = "_blank") the link opens in the browser instead. |
|
a.uri |
Not supported. |
Not supported. |
|
Not supported. |
|
Not supported. |
|
Not supported. |
|
Not supported. |
|
Behavior change. The createLink and insertImage commands don't create a UI. The saveAs and open commands are not supported. |
|
Behavior change. The createLink and insertImage commands don't create a UI. The saveAs and open commands are not supported. |
|
Behavior change. The createLink and insertImage commands don't create a UI. The saveAs and open commands are not supported. |
|
Behavior change. The createLink and insertImage commands don't create a UI. The saveAs and open commands are not supported. |
|
Behavior change. The createLink and insertImage commands don't create a UI. The saveAs and open commands are not supported. |
|
Behavior change. The createLink and insertImage commands don't create a UI. The saveAs and open commands are not supported. |
|
Behavior change. Content is filtered as through it was processed by the toStaticHTML method. Trying to inject HTML that contains an unknown element, event handlers, script or references to script, or unknown CSS pseudo-elements and pseudo-classes causes an exception when you add the HTML to the page's DOM. For more info, see Making HTML safer: details for toStaticHTML. |
|
Behavior change. Content is filtered as through it was processed by the toStaticHTML method. Trying to inject HTML that contains an unknown element, event handlers, script or references to script, or unknown CSS pseudo-elements and pseudo-classes causes an exception when you add the HTML to the page's DOM. For more info, see Making HTML safer: details for toStaticHTML. |
|
Behavior change. Content is filtered as through it was processed by the toStaticHTML method. Trying to inject HTML that contains an unknown element, event handlers, script or references to script, or unknown CSS pseudo-elements and pseudo-classes causes an exception when you add the HTML to the page's DOM. For more info, see Making HTML safer: details for toStaticHTML. |
|
Behavior change. Content is filtered as through it was processed by the toStaticHTML method. Trying to inject HTML that contains an unknown element, event handlers, script or references to script, or unknown CSS pseudo-elements and pseudo-classes causes an exception when you add the HTML to the page's DOM. For more info, see Making HTML safer: details for toStaticHTML. |
|
Behavior change. Content is filtered as through it was processed by the toStaticHTML method. Trying to inject HTML that contains an unknown element, event handlers, script or references to script, or unknown CSS pseudo-elements and pseudo-classes causes an exception when you add the HTML to the page's DOM. For more info, see Making HTML safer: details for toStaticHTML. |
|
Not supported. |
|
Not supported. |
|
Not supported. |
|
Behavior change.
|
|
Behavior change. Content is filtered as through it was processed by the toStaticHTML method. Trying to inject HTML that contains an unknown element, event handlers, script or references to script, or unknown CSS pseudo-elements and pseudo-classes causes an exception when you add the HTML to the page's DOM. For more info, see Making HTML safer: details for toStaticHTML. |
|
Behavior change. Content is filtered as through it was processed by the toStaticHTML method. Trying to inject HTML that contains an unknown element, event handlers, script or references to script, or unknown CSS pseudo-elements and pseudo-classes causes an exception when you add the HTML to the page's DOM. For more info, see Making HTML safer: details for toStaticHTML. |
|
Not supported. |
|
Behavior change. For Windows Runtime apps using JavaScript, this property returns the web-standards based DOMParser object instead of the ActiveX-based object. |
|
Behavior change. The title element doesn't render. |
|
Not supported. (This method works when your app is in development mode, though, so that you can use it to debug.) |
|
Terminates the app. You can call it only from local context pages. |
|
Not supported. |
|
Not supported. |
|
Not supported. |
|
Not supported. |
|
Not supported. |
|
Not supported. |
|
Behavior change. This method can be used to execute only JavaScript. It can't be used to execute VBScript. |
|
Not supported. |
|
Not supported. |
|
Not supported. |
|
Not supported. |
|
Not supported. |
|
Not supported. |
|
Not supported. |
|
Not supported. |
|
Not supported. |
|
Not supported. |
|
This property appears to work, but data is lost when the app is terminated. Do not use this property to store app state. |
|
Not supported. |
|
Not supported. |
|
Not supported. |
|
Not supported. |