Hi Jeff,
This looks like a bug in IE and it happens on a pre-release version of VS. We would recommend to do the development on a better tested configuration (like Win7 and VS 2012 / 2010).