Fixing Internet Explorer

Browsers251 words2 minutes to read

I came across Geek Aggregator through a link from

The posting is by someone who is involved somehow with the IE/Win development team. The question asks: What do you want from the Internet Explorer team? Here’s what a list of what I put. Feel free to add your comments as well, as I’m interested in seeing what other people think.

  • Full CSS1 and CSS 2/2.1 support.
  • Support for the application/xhtml+xml mime type.
  • Full PNG support.
  • As much of the CSS3 recommendation (not working draft) support as possible.
  • Fix the CSS bug that requires “position:relative;” to fix IE-only bugs in pure XHTML+CSS layouts.
  • Support the standard DOM 0, 1, and 2.
  • Built-in SVG support.
  • Complete support for XML, XSLT, XSL:FO, XForms, XLink, and other emerging XML-based standards.

A few posts later addressed some of the issues that the IE team had expressed concern over.

Another thing that the commenters generally aren’t thinking of is “how to get adoption.” I keep pointing out that if we fixed the CSS and PNG issues, you still wouldn’t be able to use those for years. Why? Cause consumers (and companies) really don’t care about those issues and won’t download a new version just cause you fixed one or two issues.

People don’t care because people don’t know! If the IE development team doesn’t implement them now, then it’ll be even longer before web designers can take advantage of current technology.

What are your thoughts? And what would you tell them to fix if you could?

Ryan Parman

Ryan Parman is an experienced Software/DevOps/Security engineer, currently living in Seattle. He is the creator of and , patented multifactor-authentication-as-a-service at , and came up with the idea of “serverless, event-driven, responsive functions in the cloud” while at AWS in 2010. Ryan's aptly-named blog, , is where he writes about ideas longer than . Ambivert. Curious. Not a coffee drinker.