This is the third and last post in the Minor Changes series; it covers changes in the final Release-to-Web (RTW) version of Internet Explorer 9.
The Release Candidate was Platform Complete, meaning that the Internet Explorer team worked hard to avoid making any changes that would impact the predictability of the web platform. Our focus was on fixing reliability and security issues to help ensure that IE9 is the most reliable and secure version of Internet Explorer ever released. As such, today’s list will be shorter than the prior two lists.
Beyond bugfixes, there are other changes that I will not be covering, please do not mistake this for a comprehensive list, and please note that I’m deliberately skipping over the big feature improvements that will be discussed on the IEBlog. Improvements in IE9 that impact issues or features previously discussed on this blog can be found by searching for the tag BetterInIE9.
- In IE8 and below, if you change the SRC of an image, the Complete property does not get reset. In IE9+, when the SRC attribute is updated, we will reset Complete property.
- Updated the About Dialog to display the Update Versions information, showing the latest installed cumulative update.
- Memory leaks in Sidebar gadgets have been mitigated.
- In IE8 and below, if a OBJECT or APPLET tag was dynamically inserted into an IFRAME by setting innerHTML, a relative codeBaseURL would be incorrectly combined. IE9 now uses the correct base URL.
- Bad parameter detection was introduced for the HttpOpenRequest API to fix compatibility with buggy applications.
- When content (image or ActiveX) is missing from a page, the filtering icon will be shown instead of the broken object icon if the TrackingProtection or ActiveX Filtering features are enabled.
- IE9 now appears in the “Turn Windows Features On or Off” applet.
- The msPinSite class now works properly on images that have multiple classnames defined.
- When the user has any Tracking Protection list enabled, the DNT: 1 request header is added to all outbound HTTP/HTTPS requests.
RTW New APIs
- Introduced the window.external.msActiveXFilteringEnabled method to allow pages to detect ActiveX Filtering.
- Introduced the window.external.msTrackingProtectionEnabled method (a simple alias for IE8’s InPrivateFilteringEnabled method) indicating whether TPLs are enabled.
- Introduced the navigator.msDoNotTrack property indicating whether TPLs are enabled.
- ActiveX controls can now participate in Tracking Protection and block requests to sites the are blocked by TPL.
QueryInterface on the site provided to your IOleObjectWithSite for IServiceProvider. QueryService for SID_STrackingProtection, ITrackingProtection Then, from any thread: call GetEnabled() or EvaluateUri() on the API. ::GetEnabled() returns whether Tracking Protection is on. EvaluateUri() returns whether an Uri is considered blocked by Tracking Protection and should not be downloaded (or connected to) by the ActiveX control.
I’ll also mention a few earlier changes that were introduced in the Beta or RC that I overlooked in earlier posts:
- Support for DirectX Page Transitions was removed for all browser modes.
- A NoInternetExplorer registry flag was added for Browser Helper Objects designed to run only in Windows Explorer.
- Introduced the TriggerFileDownload API to allow browser add-ons to trigger a file download without navigating a new tab.
- In IE9 mode, OBJECT tags hosting HTML are treated as IFRAMES. This enables cross-origin DATA which is blocked in other modes.
- Non-Internet Explorer hosts of the Web Browser control use software rendering mode by default, even when hardware acceleration is available. Applications can set FEATURE_GPU_RENDERING to opt-in to hardware acceleration, if the user’s hardware is compatible.
- FEATURE_BROWSER_EMULATION now supports 9000 and 9999 tokens.
- FEATURE_IVIEWOBJECTDRAW_DMLT9_WITH_GDI allows applications hosting the WebBrowser Control to get legacy rendering behavior when calling IViewObject::Draw.
- Authenticode signatures using MD2 or MD4 algorithms are rejected (by IE8 and IE9) on Windows 7 SP1.
- When you use Save Picture As on an image that was delivered with a Vary: * or other header that forbids caching (or an IMG whose source is a DataURI), IE9 will allow you to save the file in PNG format. IE8 and below only offer saving in BMP format.
- IE9 Compatibility Cookbook
- Getting your site ready for IE9
- What’s New in IE9
- IE9 Release Notes
I hope you enjoy Internet Explorer 9!