Skip to main content

How IE6 is still causing headaches and bothering the rest of us

So you have this well known security issue called content sniffing in MS IE 6. No one really cares about that anymore right? Unfortunately, when you are a top 5 website, then you kinda have to care, since 3,46% of the readers of Wikipedia, so a whopping 13.88 million of the unique monthly visitors still use Microsoft Internet Explorer 6.

You try to fix this bug. Three times, causing three software releases (1.16.3, 1.16.4, 1.16.5) in 4 weeks. And then by accident, it becomes so strict that it breaks many of the requests for all Internet Explorer versions, simply because the url contains a dot. Sigh....

THIS is why you should help all your friends to get rid of IE6.
Labels:

Comments

  1. AnonymousMay 10, 2011 at 3:03 AM

    And worse, during today's bug triage, there was speculation that this problem is causing problems for non-IE6 browsers when the response that MW gives to IE6 browsers is cached.

    ReplyDelete
  2. BawolffMay 10, 2011 at 5:40 AM

    I agree, IE6 is just evil.

    evil evil evil.

    ReplyDelete

Post a Comment

Popular posts from this blog

5 years of Article message boxes

Do you recognize these boxes ? Most likely you do. These are the very recognizable "amboxes", which is a short for " Article message boxes ". They are often visible at the top of articles in English Wikipedia and one of the most recognizable elements of those articles. Today I noticed that these boxes are now just over 5 years (and a month) old. They were first introduced to the general public starting from September 2007 . Their features are in short; a single consistent design, color coded for severity and purpose, dynamic but consistent in width (stackable), IE 5.5 and IE 6.0 compatible and a consistent parameter setup for its content. And that is a big deal, because I still remember what it looked like before when it had none of that. There were dozens of templates with different widths, different colors, different spacing and they all had different parameters. [I've been trying to find an image from back then, but I haven't been able to find one....
1 comment
Read more

kAMDReceiveMessageError

We kept running into a kAMDReceiveMessageError in our company, when trying to install adHoc iPhone apps with the iPhone Configuration Utility for Windows. Everything was fine if people tried to install using Windows iTunes. After much time it was tracked to the addition of UIRequiredDeviceCapabilities to the Info.plist. For some very strange reason it seems that the Windows ICU doesn't like that property at all and fails to install any app that carries it. Not sure if this will affect AppStore submission, iTunes handles it and so does the Mac version of ICU it seems, but it is at the very least mildly annoying that testers can't install our application using Windows ICU.
Post a Comment
Read more

Using git svn on El Capitan

I needed to use git svn to do a svn migration, and it was a very painful experience to figure out how to get that working again after I upgraded to El Capitan. It seems that with Apple's system integrity, Apple has broken both ruby and perl setups to some degree, and it's taking a while to catch up with that. Short story: Install homebrew Install ruby from homebrew Install svn using homebrew Install a new version of git using homebrew. Now you still get an error: Can't locate SVN/Core.pm in @INC (you may need to install the SVN::Core module) For this, run the following, to create some symlinks that are required for perl. sudo mkdir /Library/Perl/5.18/auto sudo ln -s /Applications/Xcode.app/Contents/Developer/Library/Perl/5.18/darwin-thread-multi‌-2level/SVN /Library/Perl/5.18/darwin-thread-multi-2level sudo ln -s /Applications/Xcode.app/Contents/Developer/Library/Perl/5.18/darwin-thread-multi‌-2level/auto/SVN /Library/Perl/5.18/auto/ Dear Apple... Reme...
Post a Comment
Read more