This page has been flagged with the following issues:
Tabbing order goes from every tab stop within the viewlink to every tab stop in the primary document, based on sequence and tabIndex value. By default, the master element participates in the tab sequence of the primary document, even if there are no tab stops defined within the viewlink. When using a viewlink, the body element inside the viewlink is not tabbable by default; the author must set the tabIndex property if the behavior is designed to display a focus rectangle on the linked document. Setting the tabIndex property on the body of the document fragment causes the onfocus and onactivate events to fire when the viewlink document body receives focus.
… further results"html" is not in the list of possible values (Canvas, CSS Font, CSS Layout, Animation, Audio, Background, Border, Box Model, CSS Attributes, CSSOM, Combinators, Deprecated, Document Structure, Exclusions, FileSystemAPI, Filters, Flexbox, Fonts, Generated and Replaced Content, Gradients, Grid Layout, HTML, Multimedia, Media Queries, Mobile, Multi-Column, Off-line Storage, Paged Media, Performance, Pointer Events, Pseudo-Classes, Pseudo-Elements, Regions, Responsive Web Design, Ruby, Scrollbar, Selectors, Security, Shapes, Syntax, Tables, Text, Touch, Transforms, Transitions, Video, Visual Effects, Web Components, WebRTC, XHR) for this property.
Related pages (MSDN)
This article contains content originally from external sources.
Portions of this content come from the Microsoft Developer Network: [Windows Internet Explorer API reference Article]