Abstract: Various embodiments provide compatibility shims that can be utilized by a web browser to dynamically change web browser platform features per domain or website. The compatibility shims can be deployed to the web browser and updated in a manner similar to that of a webpage. In one or more embodiments, the compatibility shims can be utilized to change a browser's behavior and/or the manner in which the browser represents itself per domain or website. Further, the compatibility shims can enable the web browser to dynamically remove or change support for web platform features. In addition, in at least some embodiments, users can apply their own compatibility shims to their own list of websites or webpages.

Abstract: Various embodiments provide compatibility shims that can be utilized by a web browser to dynamically change web browser platform features per domain or website. The compatibility shims can be deployed to the web browser and updated in a manner similar to that of a webpage. In one or more embodiments, the compatibility shims can be utilized to change a browser's behavior and/or the manner in which the browser represents itself per domain or website. Further, the compatibility shims can enable the web browser to dynamically remove or change support for web platform features. In addition, in at least some embodiments, users can apply their own compatibility shims to their own list of websites or webpages.

Abstract: Various embodiments provide compatibility shims that can be utilized by a web browser to dynamically change web browser platform features per domain or website. The compatibility shims can be deployed to the web browser and updated in a manner similar to that of a webpage. In one or more embodiments, the compatibility shims can be utilized to change a browser's behavior and/or the manner in which the browser represents itself per domain or website. Further, the compatibility shims can enable the web browser to dynamically remove or change support for web platform features. In addition, in at least some embodiments, users can apply their own compatibility shims to their own list of websites or webpages.

Abstract: Extensible markup language layout and rendering behaviors are disclosed. A core engine provides existing layout and rendering behaviors for a predetermined markup language, such as HTML. External components are designed to provide extended layout and/or rendering behaviors, in addition to the behaviors of the core engine. A mechanism, which can be part of the core engine, extends the existing behaviors with the behaviors of the external components. The behaviors of the external components can participate with the behaviors of the core engine.

Abstract: Various embodiments provide compatibility shims that can be utilized by a web browser to dynamically change web browser platform features per domain or website. The compatibility shims can be deployed to the web browser and updated in a manner similar to that of a webpage. In one or more embodiments, the compatibility shims can be utilized to change a browser's behavior and/or the manner in which the browser represents itself per domain or website. Further, the compatibility shims can enable the web browser to dynamically remove or change support for web platform features. In addition, in at least some embodiments, users can apply their own compatibility shims to their own list of websites or webpages.

Abstract: Various embodiments provide compatibility shims that can be utilized by a web browser to dynamically change web browser platform features per domain or website. The compatibility shims can be deployed to the web browser and updated in a manner similar to that of a webpage. In one or more embodiments, the compatibility shims can be utilized to change a browser's behavior and/or the manner in which the browser represents itself per domain or website. Further, the compatibility shims can enable the web browser to dynamically remove or change support for web platform features. In addition, in at least some embodiments, users can apply their own compatibility shims to their own list of websites or webpages.

Abstract: Various embodiments provide compatibility shims that can be utilized by a web browser to dynamically change web browser platform features per domain or website. The compatibility shims can be deployed to the web browser and updated in a manner similar to that of a webpage. In one or more embodiments, the compatibility shims can be utilized to change a browser's behavior and/or the manner in which the browser represents itself per domain or website. Further, the compatibility shims can enable the web browser to dynamically remove or change support for web platform features. In addition, in at least some embodiments, users can apply their own compatibility shims to their own list of websites or webpages.

Abstract: Extensible markup language layout and rendering behaviors are disclosed. A core engine provides existing layout and rendering behaviors for a predetermined markup language, such as HTML. External components are designed to provide extended layout and/or rendering behaviors, in addition to the behaviors of the core engine. A mechanism, which can be part of the core engine, extends the existing behaviors with the behaviors of the external components. The behaviors of the external components can participate with the behaviors of the core engine.

Abstract: Extensible markup language layout and rendering behaviors are disclosed. A core engine provides existing layout and rendering behaviors for a predetermined markup language, such as HTML. External components are designed to provide extended layout and/or rendering behaviors, in addition to the behaviors of the core engine. A mechanism, which can be part of the core engine, extends the existing behaviors with the behaviors of the external components. The behaviors of the external components can participate with the behaviors of the core engine.

Abstract: A View Template allows a template author to create an attractive HTML view template, and flow an arbitrary HTML content document into a series of containers defined in the view template. A content document author creates a standard HTML markup language document that can be displayed in a browser in the bottom-less page model. A view template author designs an HTML view template document that changes how that content document is displayed in the browser or printed. The HTML content document is “flowed” into areas defined by the HTML view template document. The HTML view template document describes where to flow the HTML content document onto the display or printer. There is an object model (OM) that supports the series of containers holding the content document. Each container in the series has a layout that defines the size, location, and ordering for the content document to flow through while in that container. The order of containers that the content document flows through is kept in a view chain.

Abstract: Extensible markup language layout and rendering behaviors are disclosed. A core engine provides existing layout and rendering behaviors for a predetermined markup language, such as HTML. External components are designed to provide extended layout and/or rendering behaviors, in addition to the behaviors of the core engine. A mechanism, which can be part of the core engine, extends the existing behaviors with the behaviors of the external components. The behaviors of the external components can participate with the behaviors of the core engine.

Abstract: A View Template allows a template author to create an attractive HTML view template, and flow an arbitrary HTML content document into a series of containers defined in the view template. A content document author creates a standard HTML markup language document that can be displayed in a browser in the bottom-less page model. A view template author designs an HTML view template document that changes how that content document is displayed in the browser or printed. The HTML content document is “flowed” into areas defined by the HTML view template document. The HTML view template document describes where to flow the HTML content document onto the display or printer. There is an object model (OM) that supports the series of containers holding the content document. Each container in the series has a layout that defines the size, location, and ordering for the content document to flow through while in that container. The order of containers that the content document flows through is kept in a view chain.