Field Notes Inside an Integrated Communications Agency

Last week on their Internet Explorer blog, Microsoft celebrated the first anniversary of Internet Explorer 7's release by putting out a post touting IE 7's rapid uptake and tightened security.

Predictably, when this hit the blogwaves some experts jumped in to question a few rather dubious claims in the post. But the real news happened a few screens down in the comments section, where a deluge of scorn and frustration was heaped on the Internet Explorer team by the general public - the regular people who use and build the Web.

Microsoft is widely regarded as being pretty good at advertising and marketing it's products, but they've occasionally been conspicuously unable to perceive irony in their messages. Microsoft proclaimed they were fighting for their "Freedom to Innovate" in response to the U.S. Department of Justice's anti-trust action a few years back... action launched of course because Microsoft's monopolistic practices were squishing innovation . But it's one thing to ignore what your customers are asking for, then brazenly lead your marketing with, "We Heard You". It's quite another to bring that kind of thinking over to your corporate blog where unhappy customers are free to call you out.

Why were users upset? Well, consider that in the time since IE 7 was released...

Firefox went 2.0, and released beta versions of 3.0. Scores of extensions - a la carte features Firefox users add in to customize their browsing experience - have been improved or newly released this year.

 

Safari released 3.0 Beta, including a new version for Windows that feels lighter, faster and smarter than IE 7.

 

The strangely overlooked Flock released a 1.0 version. While IE 7 finally adds the same level of RSS support other browsers have had for years, Flock gets social media right, and is a glimpse of what IE might look like three versions from now.

 

Opera has committed support for next-generation technologies like HTML 5, SVG and future versions of JavaScript, while IE is still struggling to fix buggy, incomplete support for decade-old standards.

 

...And for the people who either want to or have to use IE, watching Microsoft let a year go by with no new improvements highlights lessons un-learned - not something to celebrate.

A special variety of animosity came from Web designers and developers who can't ignore IE because of it's broad market share, but are growing weary making Web pages for 2008 that have to work in browsers from 2001 (IE 6), and are frustrated with lack of progress in IE 7. Microsoft realizes it needs these people - what could MS have been thinking when they provided the time, place and catalyst to turn them into an angry mob? They might as well have handed out the pitchforks and torches!

You can learn from your customers with your corporate blog. When it's time for a mea culpa, your corporate blog might not be a bad place to put it out there (hint, hint). Your corporate blog can be a very powerful weapon in your communications arsenal, but as with any weapon, it's never a good idea to point it at your own foot.

 

If you've been into the development game for any time at all, chances are you've encountered the famed Suckerfish dropdown navigation system at some point. I have successfully employed this chunk-o-brilliance - and it's successor, Son of Suckerfish - more than a few times. I recently had cause to implement dropdown navigation over Flash content, and was dismayed to see Safari comPLETEly freak out and throw a tantrum, causing my dropdown menu items to flicker in and out of existence. After much poking about, I decided that Safari must just not handle z-index as well as other browsers. I set up a little javascript function to detect the user's browser, and point to a separate CSS file if Safari was encountered.

It was only after pausing for a moment of silent reflection for all those users who would never see my handy navigation that I thought to try to find a similar case online. I started at the top of my bookmarks. Four sites in, and right there, at the top of Adobe.com , was my answer.

In order to make all other browsers behave when rendering your dropdown nav over Flash content, all you have to do is a) make use of the wmode tag for your Flash div, setting it to either transparent or opaque, and b) assign a z-index value of 2 to the block-level element containing your dropdown menu. Safari balks. To make it behave, you have to burrow down into your nav CSS and add z-index tags to every nested element, including the links:

#navdiv {
    z-index:2;
} 

#navdiv ul {
    z-index:3;
}

#navdiv ul li {
    z-index:4;
}

#navdiv ul li ul {
    z-index:5;
}

#navdiv ul li ul li {
    z-index:6;
}

#navdiv a {
    z-index:7;
}

Presto! Change-o! Safari's nasty flicker is tamed. Lesson to be learned here: take advantage of Firebug , and don't worry about reinventing the wheel. I was able to find a working example of what I wanted, and Firebug gave me the behind-the-curtain insight needed to make it happen. If you are not currently in the know on the incredible development resource that is Firebug, I implore you - drop everything and go get it!