Please, keep checking the browser's layout engine against HTML5 support:
http://en.wikipedia.org/wiki/Comparison_of_layout_engines_%28HTML5%29[
^].
From the table shown in the above article you will see that the Trident engine (
http://en.wikipedia.org/wiki/Trident_%28layout_engine%29[
^]) used in IE still sucks :-).
There is one work-around: you can change the default Web browser used by Visual Studio.
You can find out how to do it in many places:
http://www.hanselman.com/blog/HowToChangeTheDefaultBrowserInVisualStudioProgrammaticallyWithPowerShellAndPossiblyPokeYourselfInTheEye.aspx[
^],
http://stevenharman.net/blog/archive/2007/08/02/setting-a-default-browser-for-visual-studio.aspx[
^],
http://bit.ly/zK0Pa6[
^].
This totally solves the problem of rendering right features during development, but think if you really need it. First, this can create a problem with the code debugger (not a big deal, it can only disrupt JavaScript debugging which still can be used with some other browsers if tuned properly). Not a big problem anyway as you can get back to IE at any time.
More importantly, do you really need those HTML5 features if IE does not support them? How about your users using IE? Anyway, you decide.
—SA