ie8whitepapers Release Rss Feed

UPDATED RELEASE: Zoom v2 (Mar 05, 2008)

Fri, 28 Aug 2009 02:00:20 GMT

*Important:* This whitepaper applied to Internet Explorer 8 Beta 1, and has been removed. For current documentation, please visit the corresponding page in the Internet Explorer SDK: [url:Making the Web Bigger: DPI Scaling and Internet Explorer 8|http://go.microsoft.com/fwlink/?LinkID=125779]

Page zoom lets you enlarge or reduce the view of a Web page to improve readability. The feature is particularly useful on really large and really small displays, and allows for scaling of content while maintaining the intended layout of the page. The first iteration of the zoom feature shipped in Internet Explorer 7; this second iteration focuses on improving the existing experience by providing a zoom experience that is higher quality, more predictable, and more persistent.

UPDATED RELEASE: WebSlices (Mar 05, 2008)

Fri, 28 Aug 2009 01:57:17 GMT

*Important:* This whitepaper applied to Internet Explorer 8 Beta 1, and has been removed. For current documentation, please visit the corresponding page in the Internet Explorer SDK: [url:Subscribing to Content with Web Slices|http://go.microsoft.com/fwlink/?LinkID=125392]

WebSlices are a new feature in Internet Explorer 8 Beta 1 for Developers for Web sites to connect with users by allowing users to subscribe to content directly within a Web page. WebSlices behave just as feeds do, where clients can subscribe to get updates and notification of changes.

*{"["}Update: 2 April 2008{"]"}* Fixed typo in code sample: Changed 'ref' to 'href' in <a rel="feedurl" href="auction.microsoft.com/item.xml">Subscribe to WebSlice</a>

UPDATED RELEASE: W3C's ARIA Support (Mar 05, 2008)

Fri, 28 Aug 2009 01:56:37 GMT

*Important:* This whitepaper applied to Internet Explorer 8 Beta 1, and has been removed. For current documentation, please visit the corresponding page in the Internet Explorer SDK: [url:Mapping ARIA Roles, States, and Properties to UI Automation|http://go.microsoft.com/fwlink/?LinkID=110263]

The W3C defines ARIA (Accessible Rich Internet Applications) as a syntax for making dynamic Web content and custom UI controls accessible. Internet Explorer 8 Beta 1 for Developers uses ARIA role, state, and property information to communicate with assistive technologies. Instead of building separate simplified Web pages for accessibility, you can use ARIA to markup your rich Web applications with roles, states, and properties.

UPDATED RELEASE: Versioning and Internet Explorer Modes (Mar 05, 2008)

Fri, 28 Aug 2009 01:56:03 GMT

*Important:* This whitepaper applies to Internet Explorer 8 Beta 1, and is therefore out of date. It will not be updated. For current documentation, please visit the corresponding page in the Internet Explorer SDK: [url:Defining Document Compatibility|http://go.microsoft.com/fwlink/?LinkID=131990]

A fundamental problem discussed during each and every Internet Explorer release is balancing new features and functionality with site compatibility for the existing Web. Versioning and Internet Explorer rendering modes address this issue by allowing Internet Explorer 8 to remain compatible with today's Web content and providing a mechanism to introduce new features and stricter standards compliance.

UPDATED RELEASE: Versioning and Cross-Document Interaction (Mar 05, 2008)

Fri, 28 Aug 2009 01:54:54 GMT

UPDATED RELEASE: User-Agent String and Version Vector (Mar 05, 2008)

Fri, 28 Aug 2009 01:52:14 GMT

*Important:* This whitepaper applied to Internet Explorer 8 Beta 1, and has been removed. For current documentation, please visit the corresponding pages in the Internet Explorer SDK: [url:Understanding User Agent Strings|http://msdn.microsoft.com/en-us/library/ms537503(VS.85).aspx], [url:The Internet Explorer 8 User-Agent String|http://blogs.msdn.com/ie/archive/2008/02/21/the-internet-explorer-8-user-agent-string.aspx], & [url:Hosting and Reuse|http://msdn.microsoft.com/en-us/library/aa752038(VS.85).aspx]

The User-Agent string is a browser's identity as reported to Web sites via HTTP traffic; the version vector is a mechanism for obtaining the Internet Explorer version number used to evaluate conditional comments. Understanding the best practices for browser detection ensures that your site continues to operate as intended when viewed by Internet Explorer 8 clients.

UPDATED RELEASE: Selectors API (Mar 05, 2008)

Fri, 28 Aug 2009 01:48:23 GMT

*Important:* This whitepaper applied to Internet Explorer 8 Beta 1, and has been removed. For current documentation, please visit the corresponding page in the Internet Explorer SDK: [url:Selecting Objects with JavaScript|http://go.microsoft.com/fwlink/?LinkID=125798]

Selectors are a query language for searching and selecting tags (elements) within a Web page. They are most commonly used in CSS for selecting a group of elements to which certain properties will be applied. In Internet Explorer 7 there is no way of executing a selector independently of CSS. The Selectors API in Internet Explorer 8 Beta 1 for Developers puts the power and flexibility of CSS selectors into the hands of Web developers for rapid element lookups.

UPDATED RELEASE: Printing Improvements (Mar 05, 2008)

Fri, 28 Aug 2009 01:47:44 GMT

*Important:* This whitepaper applied to Internet Explorer 8 Beta 1, and has been removed. For current documentation, please visit the following article in the Internet Explorer SDK on MSDN: "CSS How-to: Optimize Pages for Printing Using CSS" [url:http://msdn.microsoft.com/en-us/library/dd433064(VS.85).aspx]

Internet Explorer 8 Beta 1 for Developers includes several print enhancements. These form the basis for a full implementation of CSS 2.1 pagination recommendations, and provide authors with more control and functionality in the print medium.

UPDATED RELEASE: Platform Performance Improvements (Mar 05, 2008)

Fri, 28 Aug 2009 01:46:50 GMT

*Important:* This whitepaper applied to Internet Explorer 8 Beta 1, and has been removed. For current documentation, please visit [url:the Internet Explorer Developer Center|http://go.microsoft.com/fwlink/?LinkID=146963&clcid=0x409]

Internet Explorer 8 Beta 1 for Developers includes several changes that improve the performance of Web sites. These changes affect many Internet Explorer subsystems, including the HTML parser, CSS rule processing, markup-tree manipulation, the JScript parser, the garbage collector, and the runtime.

UPDATED RELEASE: Per-Site ActiveX Controls (Mar 05, 2008)

Fri, 28 Aug 2009 01:43:58 GMT

*Important:* This whitepaper applies to Internet Explorer 8 Beta 1, and has been removed. For current documentation, please visit the corresponding page in the Internet Explorer SDK: [url:Per-Site ActiveX Controls|http://msdn.microsoft.com/en-us/library/dd433050(VS.85).aspx]

Internet Explorer 8 Beta 1 for Developers allows for greater control of where and under what context ActiveX controls can run. In this version of Internet Explorer, ActiveX controls that are embedded as Web objects are presented to user as add-ons. Through the Manage Add-ons dialog, the registry, or ATL SiteLock, these add-ons can be restricted for use on specific Web sites.

*{"["}Update: 3 April 2008{"]"}* Updated link to SiteLock template (v1.14).

UPDATED RELEASE: Non-Admin ActiveX Controls (Mar 05, 2008)

Fri, 28 Aug 2009 01:43:26 GMT

*Important:* This whitepaper applies to Internet Explorer 8 Beta 1, and has been removed. For current documentation, please visit the corresponding page in the Internet Explorer SDK: [url:Non-Admin ActiveX Controls|http://msdn.microsoft.com/en-us/library/dd433049(VS.85).aspx]

Internet Explorer 8 Beta 1 for Developers removes administrative involvement from the control-installation process for many existing and future ActiveX controls. This solution addresses issues raised by customers regarding previous versions, where administration of controls was not optimal.

UPDATED RELEASE: Manage Add-ons (Mar 05, 2008)

Fri, 28 Aug 2009 01:38:24 GMT

*Important:* This whitepaper applied to Internet Explorer 8 Beta 1, and has been removed. For current documentation, please visit the corresponding pages in the Internet Explorer SDK: [url:Browser Extensions|http://go.microsoft.com/fwlink/?LinkId=163060] & [url:Search Provider Extensibility in Internet Explorer|http://msdn2.microsoft.com/en-us/library/ms532996.aspx#spe_refer]

The add-on management experience in Internet Explorer 8 has been updated to let users more easily find, research, and manage the toolbars and controls that run within the browser. This document describes how to best author an add-on so that users of Internet Explorer are more likely to understand what the add-on does, who wrote it, and why they should keep it enabled on their system.

UPDATED RELEASE: Manage Add-ons (Mar 05, 2008)

Fri, 28 Aug 2009 01:37:48 GMT

*Important:* This whitepaper applied to Internet Explorer 8 Beta 1, and has been removed. For current documentation, please visit the corresponding pages in the Internet Explorer SDK: [url:Browser Extensions|http://go.microsoft.com/fwlink/?LinkId=163060] & [url:Search Provider Extensibility in Internet Explorer
|http://msdn2.microsoft.com/en-us/library/ms532996.aspx#spe_refer]

The add-on management experience in Internet Explorer 8 has been updated to let users more easily find, research, and manage the toolbars and controls that run within the browser. This document describes how to best author an add-on so that users of Internet Explorer are more likely to understand what the add-on does, who wrote it, and why they should keep it enabled on their system.

UPDATED RELEASE: Loosely-coupled Internet Explorer (Mar 05, 2008)

Fri, 28 Aug 2009 01:21:29 GMT

*Important:* This whitepaper applied to Internet Explorer 8 Beta 1, and has been removed. For current documentation, please view the corresponding entry on the Internet Explorer Team blog: [url:IE8 and Loosely-Coupled IE (LCIE)|http://go.microsoft.com/fwlink/?LinkID=125795]

Loosely-coupled Internet Explorer, or LCIE, is an architectural effort to improve the browser by separating its components and loosening their dependence on one another. Most notably, the Internet Explorer frame and its tabs are isolated into separate processes. In Windows Internet Explorer 8 Beta 1 for Developers, this isolation will allow improved performance and scalability, and richer ways to recover from failures (including crashes and hangs).

UPDATED RELEASE: Loosely-coupled Internet Explorer (Mar 05, 2008)

Fri, 28 Aug 2009 01:21:13 GMT

UPDATED RELEASE: Improved Protected Mode API Support (Mar 05, 2008)

Fri, 28 Aug 2009 01:16:57 GMT

*Important:* This whitepaper applied to Internet Explorer 8 Beta 1, and has been removed. For current documentation, please visit the corresponding pages in the Internet Explorer SDK: [url:IEGetProtectedModeCookie Function|http://msdn.microsoft.com/en-us/library/cc196998(VS.85).aspx], [url:IESetProtectedModeCookie Function|http://msdn.microsoft.com/en-us/library/cc197007(VS.85).aspx], & [url:NewProcess Event|http://msdn.microsoft.com/en-us/library/cc891504(VS.85).aspx]

Internet Explorer 8 Beta 1 for Developers makes it easier for developers to programmatically start, interact, and maintain a Protected-Mode Internet Explorer process. Building off of User Account Control (UAC) integration in Internet Explorer 7, the IWebBrowser2 interface provides new process-creation methods that properly conform to user privilege levels. Developers can now spawn and control Protected-Mode Internet Explorer processes, and avoid confusing workarounds, with a low-cost change to existing code.

UPDATED RELEASE: Improved Namespace Support (Mar 05, 2008)

Fri, 28 Aug 2009 01:16:12 GMT

UPDATED RELEASE: HTML Improvements and ACID2 (Mar 05, 2008)

Fri, 28 Aug 2009 01:03:45 GMT

*Important:* This whitepaper applied to Internet Explorer 8 Beta 1, and has been removed. For current documentation, please visit the corresponding page in the Internet Explorer SDK: [url:HTML Enhancements in Internet Explorer 8|http://go.microsoft.com/fwlink/?LinkID=125792]

HTML uses elements to represent both structure and meaning in a document. To help developers take full advantage of the elements that HTML 4 offers, and to better provide the semantic meaning intended by Web author, Internet Explorer 8 Beta 1 for Developers has upgraded support of the P and OBJECT presentational elements. Through improved support of these HTML elements, Web developers may build more expressive and accessible HTML markup.

UPDATED RELEASE: DOM Core Improvements (Mar 05, 2008)

Fri, 28 Aug 2009 01:03:10 GMT

*Important:* This whitepaper applied to Internet Explorer 8 Beta 1, and has been removed. For current documentation, please visit the corresponding page in the Internet Explorer SDK: [url:HTML and DOM Standards Compliance|http://blogs.msdn.com/ie/archive/2008/04/10/html-and-dom-standards-compliance-in-ie8-beta-1.aspx]

During Internet Explorer 6's long tenure as the leading market-share holder, Web developers revealed many bugs and inconsistencies in Internet Explorer's DOM. Today, with the Internet Explorer 8 versioning plan, these bugs and inconsistencies are corrected by default, and those customers who choose to opt out of this behavior may enable IE7 compatibility mode.

UPDATED RELEASE: Developer Tools (Mar 05, 2008)

Fri, 28 Aug 2009 01:01:46 GMT

*Important:* This whitepaper applied to Internet Explorer 8 Beta 1, and has been removed. For current documentation, please visit the corresponding page in the Internet Explorer SDK: [url:Discovering the Internet Explorer 8 Developer Tools|http://go.microsoft.com/fwlink/?LinkID=125790]

Internet Explorer 8 Beta 1 for Developers includes tools that Web developers need to efficiently debug their sites directly in Internet Explorer. Developers can immediately debug a site's HTML, CSS, and JScript from within Internet Explorer 8, rather than switch between Internet Explorer and a separate development environment. In addition, Internet Explorer 8 Developer Tools help developers identify why their site does not render or behave as expected. Finally, by making it simple to edit any site, Internet Explorer 8 Developer Tools makes experimentation and iterative development easy.