Google's Chrome accounts only for about 4 percent of browser usage worldwide, but in 2009, it exerted outsized influence.

Google launched the open-source browser in 2008, prompting many to ask why anyone needed another after Microsoft's Internet Explorer, Mozilla's Firefox, and Apple's Safari. But over the course of 2009, Google answered that question: with Chrome, the company wants not just to speed up the Web but to rebuild its foundations.

Chrome started out as one of Google's efforts to accelerate the Web--launching faster, loading pages faster, and running Web-based JavaScript programs faster. Google's argument: a faster Web experience means people will spend more time online, do more things, and, naturally, click more Google search ads.

Another worthy addition is the new Speed Dial feature (pictured above). Speed Dial improves on Safari 4's similar Top Sites feature by virtue of being more configurable. You can customize the page that appears whenever you open a new tab in Opera so that anywhere from 4 to 24 of your favorite Web sites display as thumbnails. That way, you can more quickly get to the sites you visit most often, with a simple click on a thumbnail. The feature is turned on by default, and the settings seem to offer no way to turn it off--not that you'd want to, though, because it has no downside.

Several Web designers are attempting to discourage the use of Internet Explorer 6, not the use of all Microsoft products, a Web design expert in Britain says.

Dan Oliver, editor of the British Web design magazine .net, said Microsoft itself is not the target of an ongoing campaign that accuses Internet Explorer 6 of damaging online expansion and enjoyment, CNN reported Thursday.

"This isn't an anti-Microsoft campaign," Oliver said. "Microsoft makes some fantastic products. The latest version of their browser is a good browser. But with regards to IE 6 ... (it) is an awful browser and no one should be using it."

CNN reported two Web monitors said up to 25 percent of online visitors use the Microsoft Web browser to access the Internet.

Microsoft itself is not promoting the use of Internet Explorer 6, instead encouraging Internet users to switch to a modern version of the U.S. company's famed Web browser.

"Microsoft has consistently recommended that consumers upgrade to the latest version of our browser," Microsoft said in a statement to CNN. "Internet Explorer 8 offers improvements in speed, security and reliability as well as new features designed for the way people use the Web."

Designing Web pages is challenging enough without having to build pages that work on every possible combination of Web browser and operating system in existence. So many Web designers choose to take the easy route and design just for the most popular browser, which is IE 6 right now.

But if you're going to focus your site on IE 6 you'll be causing some problems for yourself:

    * When IE 7 comes out, your site will need to be redesigned.
    * People who use other browsers won't get a good experience.
    * If new browsers come out and gain popularity, chances are your site won't be able to support them.

Standards-Based Web Design Is Best
If you design for Web standards then your Web site will be functional with every browser that supports those standards. And even long into the future, your site will stay functional.

But Internet Explorer 6 and 5 are not standards compliant. So what do you do? The common response is to design just for them and then try to force your site to look okay in standards compliant browsers like Firefox, Safari and Opera. But this is both backwards and difficult.

How to Design for Internet Explorer

   1. Build your site for Firefox or Safari first.
      Build your site and test it using Firefox or Safari first. This will insure that your Web pages look good in standards compliant browsers. And it's actually fairly easy to do.
   2. Use a DOCTYPE.
      I prefer to use XHTML 1.0 Transitional, but another good one is HTML 4.01. By using a DOCTYPE, you insure that your page isn't displayed in quirks mode, and the browsers act the same.
   3. Once you've got it looking perfect for Firefox, then start editing for IE 6 or 5.
      IE 6 or 5 should come last because it's not standards compliant. When IE 7 comes out, your page will look correct because it looks correct in the other standards compliant browsers.
   4. Don't use hacks to design for IE.
      Instead, use the cascade and valid CSS properties and selectors that IE 6 and 5 don't recognize to hide styles for standards compliant browsers. Put the IE 6 styles first in the cascade - then the standard-compliant properties.

Hiding Styles from IE 6

It's actually really easy to hide styles from IE 6 but make them visible to standards compliant browsers. Use child selectors.

In one design I built, I created a two column layout that required margins and padding. This meant that I was hitting the box model differences when I viewed the page in IE 6. My first CSS style sheet for Firefox included a line like this:

    div#nav { width: 150px; margin-left: 20px; }

This made the page line up perfectly in Firefox and Safari, but in IE the nav column was pushed over to the right too far.

So, I converted the line to use child selectors. The #nav div is a child of the body tag, so I changed the line to read:

    body > div#nav { width: 150px; margin-left: 20px; }

Of course, doing this made the #nav div lose all it's properties in IE, so I needed to add in some IE styles to get IE 6 looking okay. I added this line to the CSS:

    #nav { width: 150px; margin-left: 10px; }

The placement of this line of CSS is important if my page is still to look good in Firefox and Safari. The IE line needs to come first. Firefox and Safari will read that line and then it will be over-ridden by the body > div#nav selector lower in the document. IE 6 will read the first line and set the styles. It will then ignore the child selector, as it doesn't recognize them. When IE 7 comes along, it will act like Firefox and Safari.

By designing for a standards-compliant browser first, and then modifying your CSS to support IE's quirks, you spend a lot less time fiddling with the design and a lot more time actually designing.