“Unlocking the beauty of the Web”. This Microsoft’s new tag line for their latest release of IE9 (in public beta). Before I talk about the effects on asp.net let’s talk about the new features of this enhanced browser.
Most of the layout changes should be pretty obvious: the menu bar has been removed and the navigation controls / address bar are now at the forefront. The compatibility view, refresh and stop buttons have been just latched on to the address bar and there are dedicated favorite and tools buttons on the far right side. We don’t need to tell you that it looks a lot like Chrome – our guess is that Google’s not exactly flattered by that since we’re actually feeling the look of IE9 more than the cartoony aesthetic of Chrome, but we realize that’s a personal preference.
There are some other cool aesthetic that’s worth mentioning though. My favorite is the pop-up information is now at the bottom and kinda copied the chrome and there is nothing wrong with that, since they probably figured that chrome is coming up with the new OS and they wanted to still be part of that.
And now for the ASP.net part, how is your code going to be affected especially in the back-end data caching and displaying. Since IE9 fully supports HTML 5.0 videos, audios, CSS and AJAX are more easy to develop and supports more libraries than the IE8, the most noticeable difference is that when you run your webservice under IE9 it makes use of built-in AJAX support for HTML 5.0 giving you faster render of HTML pages.
Since right now it’s still in BETA mode , there’s more fixes and bugs to be expected, but for trial and curiosity as most of us developers like to be part of here is a download for the new IE9 ready for testdrive.
So what about this new HTML 5.0? I’ve been ask many times about this new release from W3 although still a draft, the new specifications are very promising, especially to Web Developers.
HTML5 is defined in a way that it is backwards compatible with the way user agents handle deployed content. To keep the authoring language relatively simple for authors several elements and attributes are not included as outlined in the other sections of this document, such as presentational elements that are better dealt with using CSS. W3
The HTML5 specification will not be considered finished before there are at least two complete implementations of the specification. A test suite will be used to measure completeness of the implementations. This approach differs from previous versions of HTML, where the final specification would typically be approved by a committee before being actually implemented. The goal of this change is to ensure that the specification is implementable, and usable by authors once it is finished.
HTML5 defines an HTML syntax that is compatible with HTML4 and XHTML1 documents published on the Web, but is not compatible with the more esoteric SGML features of HTML4, such as processing instructions and shorthand markup as these are not supported by most user agents. Documents using the HTML syntax are almost always served with the
text/html media type.
HTML5 also defines detailed parsing rules (including “error handling”) for this syntax which are largely compatible with popular implementations. User agents must use these rules for resources that have the
text/html media type. Here is an example document that conforms to the HTML syntax:
HTML5 also defines a
text/html-sandboxed media type for documents using the HTML syntax. This can be used when hosting untrusted content.
The other syntax that can be used for HTML5 is XML. This syntax is compatible with XHTML1 documents and implementations. Documents using this syntax need to be served with an XML media type and elements need to be put in the
http://www.w3.org/1999/xhtml namespace following the rules set forth by the XML specifications. [XML]
Below is an example document that conforms to the XML syntax of HTML5. Note that XML documents must be served with an XML media type such as
Here are a run down of the new features taken from PHP Guru’s site