This article includes the release notes for Windows Internet Explorer 8 Beta 2.

Back to the top

Compatibility with third-party applications

HP Smart Web Printing

Internet Explorer 8 Beta 2 displays a compatibility warning when certain versions of the HP Smart Web Printing add-in are installed. This issue occurs because Internet Explorer 8 Beta 2 and specific versions of this add-in are incompatible, and the installation is unstable. When you disable this add-in, the functionality that this product provides is removed.

For more information and for updates, visit the following HP Smart Web Printing Web site:

Google Toolbar

Internet Explorer 8 Beta 2 displays a compatibility warning when certain versions of the Google Toolbar add-in are installed. This issue occurs because Internet Explorer 8 Beta 2 and specific versions of this add-in are incompatible, and the installation is unstable. When you disable this add-in, the functionality that this product provides is removed.

For more information and for updates, visit the following Google Toolbar Web site:

Roxio Drive Letter Access

Internet Explorer 8 Beta 2 displays a compatibility warning when certain versions of the Drive Letter Access (DLA) add-in are installed. This issue occurs because Internet Explorer 8 Beta 2 and specific versions of this add-in are incompatible, and the installation is unstable. When you disable this add-in, the main functionality of the DLA product is unaffected.

For more information and for updates, visit the following Roxio Web site:

Skype

Internet Explorer 8 Beta 2 displays a compatibility warning when certain versions of the Skype add-in are installed. This issue occurs because Internet Explorer 8 Beta 2 and specific versions of this add-in are incompatible, and the installation is unstable. When you disable this add-in, the main functionality of the Skype product is unaffected.

Make sure that your version of the Skype add-in is 2.2.0.193 or a later version. To do this, click the Tools menu in Internet Explorer, point to Manage Add-ons, and then click Enable or Disable Add-ons.

For more information and for updates, visit the following Skype Web site:

Visual Studio .NET

Internet Explorer 8 Beta 2 and Visual Studio .NET (version 7.0 from 2002) are currently incompatible. If you install Internet Explorer 8 Beta 2, Visual Studio .NET will crash. No workaround is currently available.

Real Networks RealPlayer 11

There is a known application compatibility issue that occurs when you use Real Networks RealPlayer 11 with a beta version of Internet Explorer 8 on Windows Vista Service Pack 1 or on Windows Server 2008. To resolve this issue, install hotfix 957055. The system automatically receives this update when you install Internet Explorer 8 Beta 2.

For more information, click the following article number to view the article in the Microsoft Knowledge Base: If you want to install both Internet Explorer 8 Beta 2 and RealPlayer 11, you must install RealPlayer 11 first.

If you install RealPlayer 11 after you install Internet Explorer 8 Beta 2, you may experience some application compatibility issues. To resolve these issues, uninstall Internet Explorer 8 Beta 2, and then reinstall it.

Windows Live Mail

Internet Explorer 8 Beta 2 is compatible with Windows Live Mail.

Netflix

There is a known compatibility issue between Internet Explorer 8 Beta 2 and Netflix. Users of Internet Explorer 8 Beta 2 cannot view On Demand movies by using Netflix. Microsoft and Netflix are working together to resolve this issue as quickly as possible. This release note will be updated as soon as this issue is resolved.

ActiveX controls that are written in Visual Basic 6.0

Because of an incompatibility issue between Internet Explorer 8 Beta 2 and the Visual Basic 6.0 runtime, any ActiveX control that is written in Visual Basic 6.0 cannot display a modal dialog box. You can switch back to Internet Explorer 8 Beta 2 from any dialog box that is opened from the ActiveX control.

Window-Eyes

If you are using the Window-Eyes screen reader, some Web sites may not be read correctly. To work around this issue, switch the Web site to Compatibility View mode by clicking Compatibility View on the Tools or Page menu.

Site compatibility

If a Web site is displayed incorrectly as a blank page or if the placement of menus, images, or text is incorrect, use Compatibility View to resolve the issue. Compatibility View displays the page in the same manner that Windows Internet Explorer 7 does.

To enable Compatibility View for specific Web sites that are not displayed correctly or that are not working, follow these steps:

1.	In Internet Explorer 8 Beta 2, open the Web site that is not displayed correctly or that does not work correctly.
2.	Click the Compatibility View icon. This icon is located to the right side of the address bar. Or, click Compatibility View on the Tools menu.

Hotmail logoff

Internet Explorer 8 Beta 2 does not always log off Hotmail completely when you click the Sign out link. To make sure that Internet Explorer logs off Hotmail, click the Hotmail Sign-In link after you log off Hotmail.

Back to the top

Known issues in Internet Explorer 8 Beta 2

ClearType reverts to "disabled" when you upgrade from Internet Explorer 7

When you upgrade from a version of Internet Explorer 7 that has ClearType enabled to Internet Explorer 8 Beta 2, ClearType is disabled. To re-enable ClearType, follow these steps.

Windows XP and Microsoft Windows Server 2003

1.	Click Start, click Run, type Inetcpl.cpl, and then click OK.
2.	In the Internet Properties dialog box, click the Advanced tab, and then click Always use ClearType for HTML under the Multimedia section.

Windows Vista

1.	Click Start, type inetcpl.cpl in the Start Search box, and then click inetcpl.cpl in the Programs list.
2.	In the Internet Properties dialog box, click the Advanced tab, and then click Always use ClearType for HTML under the Multimedia section.

Issues that occur with Windows Search

Internet Explorer 8 Beta 2 has a new address bar that searches the titles and addresses of the history, the Favorites, and the RSS feeds as you type. This feature enables you to find the sites that you want quickly and easily. This feature works best when Windows Search is installed and is enabled.

Internet Explorer 8 Beta 2 works with Windows Search 3 and with later versions of Windows Search. Windows Vista already contains Windows Search 3. You can use any Windows operating system to add Windows Search 4 to obtain the full benefit of the address bar search functionality.

To obtain Windows Search, visit the following Microsoft Web site: For more information about Windows Search, visit the following Microsoft Web site: Internet Explorer 8 Beta 2 automatically starts to use Windows Search for the address bar search procedure as soon as Windows Search is installed. Internet Explorer 8 Beta 2 and Windows Search can be installed in any order.

If you experience stability or performance problems with Windows Search 3, we recommend that you upgrade to Windows Search 4. This process resolves many issues that are associated with Windows Search 3.

To obtain Windows Search 4, visit the following Microsoft Web site: In Internet Explorer 8 Beta 2, the iehistory://{GUID} and ierss://{GUID} search scopes are added to Windows Search. These search scopes are listed in the Indexing Options control panel. These search scopes are updated to have better names and icons in Internet Explorer 8 Beta 2. These search scopes cannot be configured or removed by users or by administrators.

If you use Internet Explorer 8 Beta 2 together with Microsoft Office Outlook 2003 or Microsoft Office Outlook 2007, the Internet Explorer address bar menu may be slow to appear. This issue occurs if Outlook is indexing lots of new e-mail message. For example, this issue may occur after the system resumes from hibernation.

If Windows Search is enabled, the Internet Explorer address bar menu limits titles and URLs to 1,024 characters. For very long URLs, this means that the URL may be truncated. Therefore, when you select the URL from the menu, the URL may not open correctly. This issue will be fixed in a later version of Internet Explorer 8.

A Web Slice may not be updated

In a Web Slice window, the current Web Slice may not be updated when you click the Refresh button. To obtain the updated content, click the Open button to see the full Web page.

Web Slices that use Basic authentication display a blank preview window without an error message.

Web sites are not copied correctly in InPrivate browsing

When you surf the Web in an InPrivate session in Windows Vista or in Windows Server 2008, the list of Web sites that are displayed in Compatibility View is not copied correctly from the separate list that is maintained for non-InPrivate sessions. (For more information, see the Compatibility View Settings command on the Page menu.)

You can make the Compatibility View list in an InPrivate session include the Web sites that were added in non-InPrivate sessions after you start InPrivate browsing. To do this, click Page, click Compatibility View Settings, and then click Close. You may also have to refresh the current page for the change to take effect.

The "Remove Branding" feature does not remove all kinds of branding

The Remove Branding feature of the Reset Internet Explorer Settings functionality does not remove all kinds of branding. This issue will be resolved in a later version of Internet Explorer 8.

Internet Explorer 8 Beta 2 may be unstable when you use the Search Suggestions feature

If you use Internet Explorer 8 Beta 2 on a 64-bit version of Windows Server 2003 or of Windows XP and if you use a search provider that uses a Search Suggestions feature, the installation may be unstable. To work around this issue, disable the Search Suggestions feature by using the Manage Add-ons option on the Tools menu.

Back to the top

Standards support

CSS Expressions is no longer supported in Internet Explorer 8 Standards mode

CSS Expressions is a proprietary extension to CSS that has a high performance cost. (CSS Expressions is also known as "Dynamic Properties.") Starting with Internet Explorer 8 Beta 2, CSS Expressions is no longer supported in Internet Explorer 8 Standards mode. CSS Expressions is still supported in Internet Explorer 7 Strict mode and Quirks mode for backward compatibility.

Alternative style sheets

Internet Explorer 8 Beta 2 now supports alternative style sheets as specified by HTML4 and by CSS2.1. You can access the alternative styles that are defined by the Web page author by using the Style menu under the Page menu or under the View menu. You can use the No Style option on either menu to disable all author styling.

Back to the top

Internet Explorer Administration Kit (IEAK) 8 Beta

To obtain the IEAK 8 Beta, visit the following Microsoft Web site: Note You can install the IEAK 8 Beta only if you have Internet Explorer 8 Beta 2 or a later version of Internet Explorer installed.

Known issues in IEAK 8 Beta

The "Add to the top of the list" option does not work

On the Favorites customization page in the Customization Wizard, you are given an option to put Favorites above the existing list on the destination computer. However, in IEAK 8 Beta, this option does not work. Favorites from the customization package are merged and are sorted with your list of Favorites when the Favorites are installed.

Accelerators may not be imported successfully

When you create a customization package, Accelerators from an .ins file are imported successfully only if the architectures of the customization package and of the .ins file are the same. IEAK 8 Beta lists the Accelerators on the Accelerators page, but it does not create a package that has the Accelerators.

This issue will be resolved in a later version of IEAK. The Customization Wizard will then be able to import Accelerators from .ins files from other architectures.

Back to the top

Group Policy support

The following known issues occur with Group Policy support in Internet Explorer 8 Beta 2:

•	[User | Computer] – Administrative Templates – Windows Components - Internet Explorer – Internet Control Panel – Advanced Page The Turn on Caret Browsing support Group Policy setting does not work in Internet Explorer 8 Beta 2. This issue will be resolved in a later version of Internet Explorer.
•	[User | Computer] – Administrative Templates – Windows Components – RSS Feeds The Turn off the feed and Web Slices list Group Policy setting does not work in Internet Explorer 8 Beta 2. The Group Policy does not affect Web Slices. RSS feeds can be controlled with this policy setting. This issue will be resolved in a later version of Internet Explorer.
•	[User | Computer] – Administrative Templates – Windows Components - Internet Explorer – Security Features The Turn off Connection Scaling Group Policy setting does not work in Internet Explorer 8 Beta 2. This issue will be resolved in a later version of Internet Explorer. The Turn off Cross Domain Request Object Group Policy setting does not work in Internet Explorer 8 Beta 2. This issue will be resolved in a later version of Internet Explorer. The Turn off Cross Domain Messaging Group Policy setting does not work in Internet Explorer 8 Beta 2. This issue will be resolved in a later version of Internet Explorer.
•	[User | Computer] – Administrative Templates – Windows Components - Internet Explorer – Delete Browsing History The Explain text for the Prevent Deleting Web sites that the User has visited Group Policy setting is incorrect. The correct Explain text is as follows: This policy setting prevents users from deleting the history of Web sites that the user has visited. This feature is available in the Delete Browsing History dialog box. If you enable this policy setting, Web sites that the user has visited are preserved when the user clicks Delete history. If you disable this policy setting, Web sites that the user has visited are deleted when user clicks Delete history. If you do not configure this policy setting, the user can decide whether to delete or to preserve Web sites that the user has visited when the user clicks Delete history. By default, if the Turn off Delete Browsing History functionality Group Policy setting is enabled, this policy is enabled. The Explain text for the Prevent Deleting Favorites Site Data Group Policy setting is incorrect. The correct Explain text is as follows: This policy setting is used to disable the Preserving favorites site data option in the Delete Browsing History dialog box. If you enable this policy setting, Favorites site data is deleted when the user clicks Delete favorites. If you disable this policy setting, Favorites site data is preserved when the user clicks Delete favorites. If you do not configure this policy setting, the user can decide whether to delete or to preserve Favorites site data when the user clicks Delete favorites. If the Turn off Delete Browsing History functionality Group Policy setting is enabled, this policy has no effect.
•	[User | Computer] – Administrative Templates – Windows Components – Internet Explorer – Security Features The Turn off Cross Document Messaging Group Policy setting does not work in Internet Explorer 8 Beta 2. This issue will be resolved in a later version of Internet Explorer.
•	[User | Computer] – Administrative Templates – Windows Components – Internet Explorer – Compatibility View The Turn off Compatibility View button Group Policy setting does not work in Internet Explorer 8 Beta 2. This issue will be resolved in a later version of Internet Explorer.

Back to the top

Known issue when you slipstream Internet Explorer 8 Beta 2

When you slipstream Internet Explorer 8 Beta 2 into a Windows Vista image, you can configure the Internet Explorer default settings. However, you cannot configure the following default settings in Internet Explorer 8 Beta 2 when it is slipstreamed:

•	The "Emulate IE7" setting In Windows System Image Manager, the Emulate IE7 setting does not work. Internet Explorer 8 Beta 2 runs in the default mode. The default mode is the Internet Explorer 8 Standards mode.
•	The "DisallowMovingStopRefreshButtons" unattended setting In Windows System Image Manager, the Microsoft-Windows-IE-InternetExplorer\DisallowMovingStopRefreshButtons unattended setting does not work. The Stop and Refresh buttons are locked, and the user cannot move them.

Back to the top

Known issues when you install Internet Explorer 8 Beta 2

Important If you are running Windows Small Business Server 2003, do not install Internet Explorer 8 Beta 2.

Command bar customizations are not migrated when you upgrade

After you upgrade from Internet Explorer 7 to Internet Explorer 8 Beta 2, the command bar is set to Internet Explorer 8 Beta 2 defaults. If you customized your command bar in Internet Explorer 7, you can re-customize the command bar in Internet Explorer 8 Beta 2. To do this, right-click the command bar, and then click Customize.

Note When you uninstall Internet Explorer 8 Beta 2, Internet Explorer 7 customizations are restored.

JScript errors may occur when you upgrade from Internet Explorer 6 on Windows XP or on Windows Server 2003

Do not upgrade from Microsoft Internet Explorer 6 to Internet Explorer 8 Beta 2 on a system that is running Windows XP or Windows Server 2003. A rare installation issue may occur in which Internet Explorer may exhibit false JScript errors and an inability to add Favorites or Web Slices.

To work around this issue, uninstall Window Internet Explorer 8 Beta 2, install Internet Explorer 7, and then upgrade to Window Internet Explorer 8 Beta 2.

The Internet Explorer 8 Beta 2 icon is missing

You upgrade from Internet Explorer 8 Beta 1 to Internet Explorer 8 Beta 2 on a computer that is running a 64-bit version of Windows Vista. When you do this, the icon for the 32-bit version of Internet Explorer 8 Beta 2 is missing in the All Programs feature on the Start menu.

You are prompted to continue installing Internet Explorer 8 Beta 2 if you previously installed Internet Explorer 8 Beta 1

On a computer that is running Windows XP, you install Internet Explorer 8 Beta 1 and then install Windows XP Server Pack 3. Then, you try to install Internet Explorer 8 Beta 2. When you do this, you receive the following message:

Troubleshooting installation problems

If you cannot install Internet Explorer 8 Beta 2, follow these steps:

1.	Restart your computer so that any pending updates that require a restart can be installed.
2.	Make sure that the Windows Update service is running. To do this, follow these steps: a. Click Start, click Run, type services.msc, and then press ENTER. b. In the Services list, locate the Windows Update service. If the Windows Update service is not running, start it.

Internet Explorer 8 Beta 2 may require the following updates, depending on the operating system that you are running. The Internet Explorer 8 Beta 2 Setup program automatically installs the necessary updates for the system.

•	Hotfix 932823: 932823 (http://support.microsoft.com/kb/932823/) You may be unable to use Windows Internet Explorer to download files on a computer that is running Windows Server 2003 or Windows XP Install this hotfix to resolve an issue in which a user cannot use Internet Explorer 7 to download files. This issue occurs on computers that are running Windows XP with Input Method Editor enabled.
•	Update 946501: 946501 (http://support.microsoft.com/kb/946501/) An access violation occurs when an application exits on a Windows XP SP2-based multi-core computer Install this update to resolve an issue in which a window that has a language bar crashes when it exits. This issue occurs on multi-core computers that are running Windows XP Service Pack 2.
•	Update 943302: 943302 (http://support.microsoft.com/kb/943302/) December 2007 Windows Vista Application Compatibility Update Install this update to resolve a set of known application compatibility issues with Windows Vista.
•	Update 956586: 956586 (http://support.microsoft.com/kb/956586/) Software updates that are required to be installed before you install Internet Explorer 8 Beta 2 on a Windows Vista-based computer
•	Update 937287: 937287 (http://support.microsoft.com/kb/937287/) A software update is available for the Windows Vista installation software feature The Internet Explorer 8 Beta 2 Setup program does not automatically install this update. However, it is a required update for x64-based versions of Windows Vista. Install this update to enable future updates to be installed successfully on all editions of Windows Vista.

When you install Internet Explorer 8 Beta 2, you may receive the following error message: To work around this issue, you must install the Internet Explorer 8 Beta 2 prerequisites manually.

Back to the top

Language support

The lists of localized terms or feature names are still to be determined for the release version of Windows Internet Explorer 8.

Internet Explorer 8 Beta 2 is available in the following languages and platforms.

Language	Platforms
Chinese (Simplified)	Windows XP x86 Windows Vista x86 Windows Vista x64 Windows Server 2003 x86 Windows Server 2003 x64
English	Windows XP x86 Windows Vista x86 Windows Vista x64 Windows Server 2003 x86 Windows Server 2003 x64
German	Windows XP x86 Windows Vista x86 Windows Vista x64 Windows Server 2003 x86 Windows Server 2003 x64
Japanese	Windows XP x86 Windows Vista x86 Windows Vista x64 Windows Server 2003 x86 Windows Server 2003 x64
Chinese (Hong Kong)	Windows XP x86 Windows Vista x86
Arabic	Windows XP x86 Windows Vista x86
Chinese (Traditional)	Windows XP x86 Windows Vista x86
Czech	Windows XP x86 Windows Vista x86
Danish	Windows XP x86 Windows Vista x86
Dutch	Windows XP x86 Windows Vista x86
Finnish	Windows XP x86 Windows Vista x86
French	Windows XP x86 Windows Vista x86
Greek	Windows XP x86 Windows Vista x86
Hebrew	Windows XP x86 Windows Vista x86
Hungarian	Windows XP x86 Windows Vista x86
Italian	Windows XP x86 Windows Vista x86
Korean	Windows XP x86 Windows Vista x86
Norwegian	Windows XP x86 Windows Vista x86
Polish	Windows XP x86 Windows Vista x86
Portuguese (Portugal)	Windows XP x86 Windows Vista x86
Portuguese (Brazil)	Windows XP x86 Windows Vista x86
Russian	Windows XP x86 Windows Vista x86
Spanish	Windows XP x86 Windows Vista x86
Swedish	Windows XP x86 Windows Vista x86
Turkish	Windows XP x86 Windows Vista x86

How to install localized versions of Internet Explorer 8 Beta 2

Windows Vista, Windows Vista Service Pack 1 (SP1), or Windows Server 2008

1.	Uninstall Internet Explorer 8 Beta 1 if it is installed.
2.	Make sure that you are installing the language version of Internet Explorer that matches the system language of Windows Vista. If the languages do not match, the Internet Explorer 8 Beta 2 user interface is displayed in English.

Windows XP Service Pack 2 (SP2) or Windows Server 2003 Service Pack 2 (SP2)

1.	Make sure that you are using the correct language version of Windows. Or, install the language package for your language.
2.	Install the version of Internet Explorer 8 Beta 2 that is correct for your language. If the languages do not match, the Internet Explorer 8 Beta 2 user interface is displayed in English.

Back to the top

How to uninstall Internet Explorer 8 Beta 2

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top

Assistive technology

Internet Explorer 8 Beta 2 is not yet fully compatible with all versions of Assistive Technology applications, including Job Access With Speech (JAWS), Window-Eyes, and ZoomText. Menu and Web content reading may not function correctly. JAWS 9.0.2169 is the first version of JAWS that is compatible with Internet Explorer 8 Beta 2.

To enable Assistive Technology programs to perform correctly before updates are available, follow these steps when you install Internet Explorer 8 Beta 2.

Warning This workaround may make a computer or a network more vulnerable to attack by malicious users or by malicious software such as viruses. We do not recommend this workaround but are providing this information so that you can implement this workaround at your own discretion. Use this workaround at your own risk.

1.	If you are running Windows Vista or Windows Server 2008, disable protected mode. To do this, follow these steps: a. On the Tools menu, click Internet Options. b. On the Security tab, click to clear the Enable Protected Mode option for the following zones: • Internet • Local intranet • Trusted sites • Restricted sites We strongly recommend that you browse only to Web sites that you trust while protected mode is disabled.
2.	Install Internet Explorer 8 Beta 2.
3.	After installation is complete, modify the registry. To do this, follow these steps. Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base: 322756 (http://support.microsoft.com/kb/322756/) How to back up and restore the registry in Windows a. Click Start, click Run, type regedit in the Open box, and then click OK. b. Locate and then click the following registry subkey: HKEY_CURRENT_USER\SOFTWARE\Microsoft\Internet Explorer\Main c. On the Edit menu, point to New, and then click DWORD Value. d. Type PPT, and then press ENTER. e. On the Edit menu, point to New, and then click DWORD Value. f. Type LCIE_FTW, and then press ENTER. g. On the Edit menu, click Modify. Note The values in these registry entries are configured to be "0" when you perform steps 3c through 3g.
4.	Start Internet Explorer 8 Beta 2. The browser prompts you for configuration information when you start it for the first time.
5.	Re-enable protected mode.

Note When you uninstall Internet Explorer 8 Beta 2, the system reverts to the earlier version of Internet Explorer, and Assistive Technology programs perform as they did previously.

Back to the top

How to use the JScript debugger with Internet Explorer 8 Beta 2

When you use the JScript debugger, be aware of the following items:

•	We do not recommend that you use the JScript debugger when multiple tabs are open. When the debugger starts, it attaches to all open tabs in an Internet Explorer instance. This condition could cause the browser to stop responding. To work around this issue, use only one tab per Internet Explorer instance when you debug.
•	When you are in a breakpoint, Internet Explorer is paused and is waiting for input from the script debugger. Therefore, it does not respond to any user interaction. The Internet Explorer window is not updated, and other Developer Tools features, such as the HTML and CSS tabs, do not function. This condition occurs because the tools depend on receiving data from Internet Explorer.
•	In some conditions, the debugger may not correctly highlight the next statement to be run.
•	The debugger does not correctly delete a breakpoint set in a function expression. (A function expression is a function that is assigned to a variable.)
•	If you click Start Debugging after you click Stop Debugging while you are in a breakpoint on the same site, Internet Explorer stops responding. Additionally, you receive the following error message: There is no source code available for the current location
•	When you click Stop Debugging while you are in a breakpoint hit before the page is completely loaded, nothing occurs. To stop debugging, click Continue, and then click Stop Debugging.
•	After you click Start debugging, JavaScript errors continue to display error dialog boxes. This behavior occurs even if you click Stop debugging. This behavior occurs regardless of the Internet Control Panel settings that control script debugging. To stop the dialog boxes from appearing, close and then reopen Internet Explorer.
•	The Locals and Watch windows do not show expandos that are added to objects.

Back to the top

How to use a profiler with Internet Explorer 8 Beta 2

When you use a profiler, be aware of the following items:

•	When you click the Start Profiling button on a multi-frame HTML page, only the top-level frame is put into profile mode. To work around this issue, refresh the page after profiling starts.
•	Profiling requires that Script debugging be enabled to display the URL and Line Number information. If Script debugging is not enabled, profiling works. However, the profiling report does not have URL and Line Number information.
•	When you export a profiler report, only the Functions view of the report is exported. All available columns are exported in a default order. This behavior occurs even if the current view of the report is set to another view.
•	When you double-click a row in the profiler report, the source code for the corresponding function is displayed on the Script tab only if the URL is available on the Script tab.
•	You cannot select multiple rows in the Call Tree view of the profiler.

Back to the top

How to use Developer Tools with Internet Explorer 8 Beta 2

When you use Developer Tools, be aware of the following items:

•	Changes that you make to the site by using the Developer Tools are not reflected in the Developer Tools user interface after you pin or unpin the tools. The changes still exist in Internet Explorer so that the display of the page does not change. However, the tools do not reflect the changes. For example, if you disable a CSS property and then pin or unpin the tools, that property remains disabled. However, the property does not appear in the Developer Tools user interface.
•	Internet Explorer stops responding if you try to perform actions that are outside the script debugger while you are in a breakpoint. For example, the Locals and Call Stack features work. However, when you change the document mode, Internet Explorer stops responding.
•	The Developer Tools use the standards-compliant rules for style application. This logic matches the logic that is used in Internet Explorer 8 Standards mode. Sometimes, this logic causes the tools to report inaccurate information for pages in Quirks mode or in Internet Explorer 7 Standards mode.
•	You cannot enable and disable style properties that are marked as "important."
•	If you start script debugging while the tools are pinned, the script debugger and Internet Explorer may stop responding. If you frequently debug script, we recommend that you keep the tools in a separate window. This is because the tools must be unpinned when you debug script.
•	When you use the Select Element by Click option in a tab other than the HTML tab, the correct node is automatically selected in the HTML tree. However, the HTML tab is not opened. You must click the HTML tab to switch from your current view.
•	The Styles and Trace Styles panes list the following properties as part of the inline style on all elements: • pixelheight • pixelleft • pixeltop • pixelwidth This behavior occurs even if those properties were not specified as inline styles by the author. This issue occurs because of an error in the Developer Tools. It does not affect how the page is displayed in Internet Explorer 8 Beta 2.
•	When you start script debugging before you enable script debugging for Internet Explorer, you receive the following error message: Unable to attach to the process. Another debugger might be attached to the process. To work around this issue, click OK, and then click Start Debugging again.

Back to the top

Known issues for developers

AJAX Navigations

Internet Explorer 8 Beta 2 creates entries in the travel log and in the back button for each instance of window.location.hash that is set. This behavior is part of the behavior for Internet Explorer 8 AJAX Navigation. If you use this technique to communicate between documents, we recommend that you switch to the Internet Explorer 8 Cross Document Messaging feature that is based on Section 6.4 of the HTML 5.0 specification.

For more information about the HTML 5.0 specification, visit the following World Wide Web Consortium Web site:

XDomainRequest

The onload event may not occur reliably. We recommend that you use the onprogress events. These events continue to occur as the data is received.

Back to the top