When a friend of mine visited the US for some reason none of the electronic fingerprint scanners could read his prints (he hadn't done anything to remove them). He was delayed for hours while being asked again and again why he had removed his fingerprints. Eventually a sensitive enough scanner was found that could read his prints. If it wasn't for that he was going to be denied entry into the US.
Someone at my last workplace had some Ivy growing in their pod. They didn't even have it in soil, it started out as just a 20cm length of vine in a plastic water bottle. A year later and with some strategic guiding along the ceiling it was growing in 5 different directions. I suspect that it grew so well partly because the lights in the building were left on at night.
IE has almost total market dominance now, that's a simple fact of life, so MS can't necessarily fix a lot of these things because it will break millions of existing websites.
At my work there's an intranet site that I need to use constantly that relies on non-standard IE DOM features. Naturally it's completely broken in Firefox. That means that, yes, Firefox supports standards better, is easier to develop for etc. but also means that nobody where I work can use it.
Standards compliance isn't the be all and end all. Why not put a compatibility layer in there (that you can switch off) to emulate the non-standard and broken behavior of IE so all these real life scenarios, as unfortunate as they are, don't stop people from migrating to firefox?
Slashdot Mirror
When a friend of mine visited the US for some reason none of the electronic fingerprint scanners could read his prints (he hadn't done anything to remove them). He was delayed for hours while being asked again and again why he had removed his fingerprints. Eventually a sensitive enough scanner was found that could read his prints. If it wasn't for that he was going to be denied entry into the US.
Someone at my last workplace had some Ivy growing in their pod. They didn't even have it in soil, it started out as just a 20cm length of vine in a plastic water bottle. A year later and with some strategic guiding along the ceiling it was growing in 5 different directions. I suspect that it grew so well partly because the lights in the building were left on at night.
IE has almost total market dominance now, that's a simple fact of life, so MS can't necessarily fix a lot of these things because it will break millions of existing websites.
At my work there's an intranet site that I need to use constantly that relies on non-standard IE DOM features. Naturally it's completely broken in Firefox. That means that, yes, Firefox supports standards better, is easier to develop for etc. but also means that nobody where I work can use it.
Standards compliance isn't the be all and end all. Why not put a compatibility layer in there (that you can switch off) to emulate the non-standard and broken behavior of IE so all these real life scenarios, as unfortunate as they are, don't stop people from migrating to firefox?
This article talks about a study which suggests the map is a fake.