I’ll say this up-front, so I don’t waste anyone’s time. I’m not an expert on Web Components, and this post isn’t intended to teach anything about them.
With that said, over the last few days I’ve been catching up on some podcasts, and the topic of Web Components has come up several times. The technology (or, I should say, technologies, since there are at least 4 different specifications encompassed by the term) sounds very interesting and useful, but the lament I heard over and over was that there’s no support for these technologies in Internet Explorer, and no indication of when they will be supported.
It’s always frustrating when you’re working on a project, and everything looks good when you’re running it from Visual Studio, and then you deploy to your web server, and suddenly something’s not rendering correctly. In this post, I’ll give you some tips for troubleshooting these problems when the target browser is Internet Explorer.
As touch becomes a more and more prevalent means of interacting with PCs as well as phones and tablets (I’m typing this on a Lenovo Carbon X1 Touch laptop), developers should be aware of how to create touch-friendly sites and apps that help users make the most of touch-enabled devices.
As many of you may be aware, you can only have one version of Internet Explorer installed at any given time (the exception being that the IE Platform Previews are able to install side-by-side with a released version of IE). Given this, Microsoft has for some time provided virtual machines for the purposes of testing applications against different versions of Internet Explorer.