A new developer-centric IE has been released, named Internet Explorer Developer Channel. This build provides an early way for developers to test webpages and can be installed side-by-side with IE.
The Status.IE project provides compatibility information for 4 major web browsers, allowing developers to see which features are available based on the browsers they need to support. Microsoft has open-sourced both the code serving the project and the data it offers, making it easy for developers to further their own development projects.
jQuery will drop support for Internet Explorer 6 and Internet Explorer 7 "somewhere in 2015", jQuery Foundation president Dave Methvin stated on the official jQuery blog last week. This change will go hand in hand with the release of jQuery 1.13. The release 1.12 will be the last one with official support for the named versions of Microsoft's default browser for Windows.
Internet Explorer 11 will not be able to properly run .NET Framework 4.0 based web applications due to an error in the browser detection mechanism, which can be either fixed by installing .NET 4.5 or by adding a .browser file with correct definitions.
Telerik has released an update to their RadControls for ASP.NET AJAX Q3 2013 control suite with support for Visual Studio 2013 and Internet Explorer 11 including several new features and bug fixes.
Internet Explorer 11 included with Windows 8.1 includes new F12 tools, support for WebGL and Hardware 3D in addition to touch improvements.
There is good news for web developers: Windows 8.1 will ship with Internet Explorer 11, which will feature WebGL, much improved developer's tools and support for Google's SPDY protocol.
Microsoft has announced increased Flash support on IE10 running on Windows 8 and Windows RT. This content will now be enabled to run by default and solidifies Flash's position on the Windows platform.
Microsoft has released modern.ie which enables you to test websites on various versions of IE with a series of tools including tips to build modern sites while supporting old versions of Internet Explorer.
Windows Security is a hard problem. There are countless optional settings that can introduce security vulnerabilities, many of which are enabled by default. The documentation for these settings are scattered with current articles freely mixed with out-of-date versions. One solution to this is the Microsoft Security Compliance Manager.
Jatinder Mann, an Internet Explorer PM at Microsoft, held the session 50 performance tricks to make your HTML5 apps and sites faster at BUILD 2012, providing many tips for creating faster web applications.
Though it really should have been done back in 2009 (the year Windows 7 was touting its touch screen support), Microsoft’s IE team has finally released their recommendations for building touch-friendly web sites.
One of the major changes in HTML 5 was the introduction of standardized parsing rules for non-standard HTML, or more specifically, mal-formed HTML. Internet Explorer will start abiding by these new parsing rules in the recently released version 10, platform preview 2.
The IE team has announced Second Platform Preview for IE10. The Preview showcases new IE features like Positioned Floats, HTML5 SandBox, HTML5 Forms, setImmediate API, Page Visibility API, Async Scripts and more. It uses the same HTML5 engine seen in the recent Windows 8 demos.
At yesterday’s keynote Microsoft was proudly displaying their first platform preview of IE 10. Amongst all the crowing about its performance enhancements a bigger issue was missed. What do they really mean by “Native HTML5”? Is it really just about hardware acceleration? We don’t think so.