Internet Explorer 9 RC to include ActiveX filtering

By Tom Warren, on 19th Jan 11 2:13 pm with 5 Comments

Microsoft’s forthcoming Internet Explorer 9 Release Candidate build will introduce an important new filtering feature, WinRumors has learned.

According to sources familiar with Microsoft’s plans, the software giant is currently building copies of Internet Explorer 9 that include an “ActiveX filter” feature. The filter will allow users to control what ActiveX elements are displayed on sites they visit, furthering Microsoft’s commitment to security within its browser. Microsoft is expected to ship the feature inside Internet Explorer 9 Release Candidate (RC).

Internet Explorer 9 ActiveX filtering

Microsoft has also improved the UI of the browser tabs and buttons in Internet Explorer 9 RC. The build features square tabs and minor UI enhancements to the address bar buttons in Internet Explorer 9. Microsoft has also updated its download manager so that it now displays the transfer speed without the need to hover over individual downloads. Microsoft is expected to release Internet Explorer 9 Release Candidate on January 28. The latest Internet Explorer 9 RC escrow build is 9.0.8073.6003.

Microsoft announced earlier this month that the beta version of Internet Explorer 9 has surpassed 20 million downloads, making it the most downloaded beta release of Internet Explorer ever. The download rate of Internet Explorer 9 beta has grown by 5 million each month since its release on September 15, 2010. Internet Explorer 9 RC is expected to include UI tweaks and minor changes to some functions in Internet Explorer. Microsoft will also introduce a new Tracking protection feature in Internet Explorer 9 RC that will allow consumers to address their concerns about being tracked on the web.

Recently, a new Internet Explorer 9 beta build leaked to the web, originally reserved for close partners and TAP testers. The build, version 9.0.8027.6000, began showing up on popular file sharing websites in late November. The leaked version includes bug fixes, stability improvements and the latest rendering engine seen in the recent developer Platform Preview. It appears, from the digital signature, that the build was compiled as recently as November 19. Microsoft’s previous Platform Preview 7 build was labeled 9.0.8023.6000. WinRumors posted exclusive screenshots of the new leaked Internet Explorer 9 beta build.

Microsoft recently released an updated platform preview build of Internet Explorer 9. Version 7 now includes 354% better JavaScript performance according to WebKit SunSpider benchmarks. In keeping with previous platform preview builds, this latest version, Platform Preview 7, does not contain the Internet Explorer 9 UI elements.

Internet Explorer 9 beta made its debut on September 15 to a fanfare of Gorillaz appearances and anticipation of Microsoft’s new look browser. The next generation browser has received a warm welcome from tech enthusiasts, developers and the media. The browser has been so popular that it grabbed 0.25% of browser market share in just two weeks.

  • GP007

    This sounds good to me, just release it already!

  • Oime

    9 days left , let’s see it looks promising !

  • Tornado7969

    I know this may be wrong, but since it is Internet Explorer “9″, and that they are doing platform previews for the first time ever, instead they are releasing the platform previews instead of extra betas to show the new improvements, which means that once it hits Platform Preview 9, that is when IE9 will be released fully!

  • Brian Hall

    I loved IE9 as a “typical user”, but as a .NET developer it really hampered me. I had to switch back to IE8 in order to be productive with my development again. I hope DevDiv and the IE team get together to work out those kinks.

  • Anonymous

    If it was “Internet Explorer 9 RC to exclude ActiveX” I’d be impressed.

    As it is…

    Microsoft has been trying to use ad hoc filtering schemes to make native code active content secure since 1997. This is just more of the same. Until they accept that they need to limit implicitly installed active content to hard interpreted sandboxes, no exceptions, they’re not going to solve the problem.