Part III – How to hunt down and patch up ie6 bugs
You are coding out a web page, you fit the styles, arrange your divs, align your margins, and check it on your browser, just to be sure that it’s correct.
It’s not.
There’s a huge hole in your layout, and you have no idea why! What do you do?
Well, you could read Part 1 of this series, and feel some solidarity with others (including me) who share your dilemma. Or you could read part 2, and employ some of the ie hacks I suggest, add an ie specific stylesheet, or try some different CSS tricks. But when none of that works, and you just cannot find the source of the ghost, you will need some serious tools.
As I have mentioned before, we test on many browsers at MoreVisibility, so our machines host a range of browsers ad web developer tools. Web developer tools are available for most browsers and are indispensable when troubleshooting layout. There is absolutely no way I would be sane, or even still working today, without my trusty Firefox and ie add-ons.
Firefox Add-ons
Firebug: https://addons.mozilla.org/en-US/firefox/addon/1843
This fantastic little tool was introduced to me by a colleague, who convinced me to ditch my old trial-and-error ways. With one click inside Firefox, a dialog box pops up within the window, showing the HTML and CSS side by side. You can mouse over an element to bring up its code, and what’s more, CSS styles are shown in hierarchical order, giving you a view of which styles are at the top of the inheritance pile. A great asset when you can’t figure out where that underline is coming from!
Mozilla Web Developer Toolbar: http://chrispederick.com/work/web-developer/
This toolbar isn’t as universally useful as Firebug, but it does pack a host of valuable tools. You can check the actual (not stated) size of an element, use the ruler and generate a great image report with a list of images, their sizes and urls.
Internet Explorer Add-on
There is only 1 proprietary application for ie in this category, and it works for all versions of ie http://www.microsoft.com/downloads/
It combines some of the tools available from both Firefox add-ons. You can view the html, but the CSS panel is often code-bloated or unspecific. There is a ruler, an outline feature, and some image options.
Ie Web Developer is essential in troubleshooting the browser, but even with its aid, you may still need to use your wiles and common sense. Happy Hunting!
Part 2 – A few tips on improving your relationship with ie and its bugs
In part 1 of this series IE 6 Reluctant friend and frequent foe – Part I, I did rant just a bit about the myriad of downsides to Internet Explorer 6 and how much this frustrates me on a daily basis. I am often tempted to pin the logo to a dartboard and let rip! However, from the hours of trouble shooting, re-coding and incoherent, angered mumbling, a few small gems of knowledge have emerged, that help me cope.
Since it looks like we will have to live with ie6 for a while, let’s cozy up and make friends. Here are some things that make ie6 happy.
{ display:inline; }
{margin:0;}
just to be sure! and
and
tags, so be sure to state all padding and margins on these elements.Hopefully this may help clear the ie fog, or at least assist you in extending an olive branch to ie6. If not, then all we can do is wait and cross-check. In my next post, I will share all our MoreVis browser cross-check and testing secrets. Hint: it involves a lot of desk hopping!!
Part I – How to troubleshoot, design, and make friends with ie6
For those of you who don’t spend your days wrestling with cross-browser compatibility (read: making the website look the same in all browsers) you may be unaware of the constant battle therein.
Of the many browser choices out in the wild world web, the three most used are Internet Explorer 6, Internet Explorer 7 and Firefox. Those three are the ones we primarily troubleshoot for here at MoreVisibility, and in doing so, attempt to ensure that the greatest number of users will be able to view our sites as the designer intended. Of course we check Safari on a Mac too, but it is rarely problematic.
So all three programs are browsers, all designed to do the same thing, turn code into a readable page, and transmit data from server to client, right? So why are there so many cross-browser issues?
That’s what I’d love to know! In programming these browsers, some companies got it right, some didn’t. A certain software conglomerate’s early browser incarnations couldn’t handle, for one, valid CSS. This means, for designers that code in CSS, a myriad of ‘hacks’ and shortcuts must be engaged to force ie6, yes you guessed it, to render the layout correctly. This is not only exhausting, but incredibly frustrating for someone who has spent hours laying out a design in, say Firefox, then switches over to ie6 to find that the right sidebar is above the header and all the links are pink!
Microsoft made many improvements in ie7, which does a far better job of paying attention to what the coder meant, but there are still bugs. In addition, not all users have upgraded to ie7 and are still browsing daily on a severely outdated browser.
Firefox is my browser of choice, and it rarely lets me down. It is an open-source software, meaning that updates and fixes come regularly, ensuring that you always have the latest and best version of the browser.
But as much as I am tempted to force users into switching to Firefox, or any standards compliant browser, the reality is that it won’t happen. I have to work around the ie6 bugs and learn from the curveballs it throws me.
In my next blog, I will share some ie6 secrets, and shed some light on how to get your layout to function in ie6 with minimal pain and wasted time!!