Liquid vs. Fixed
As it turns out, Jeremy Keith seems to be one of the most vigorous supporters of liquid layouts I've ever met. So, not surprisingly, he has once again broached the subject over on hist blog.
Jeremy suggests that it is "monkey see, monkey do" at the root of the problem. However, it most likely goes much deeper than this.
We are just now starting to have designers who have designed for the web their whole life and are not influenced by any sort of print or traditional background. Additionally, due to advancements in blogging tools and other frameworks it has become easier and easier for anyone to build a dynamic web site without any kind of true programming knowledge.
This has lowered the barrier to entry for many designers, and they can make the jump from print and other traditional medias with increasingly less effort.
Ok. So what's the point?
Designing for traditional media allows for very exacting control over a design, typography, colors, size, and more. Until the web came along, a designer never had to worry about variables such as screen resolution, limited color palettes, or the availability of their favorite font on every machine.
Is it any surprise that those designers do not want to relinquish that control? Of course not, that is how they are used to working, and the web doesn't want to cooperate (Yet).
Embracing the Web
You will never hear someone complain about how easy it is to publish new content on the web, but they will complain about the afore-mentioned lack of control. So why doesn't anybody ever complain that their latest poster doesn't automatically publish and mail itself to their audience? Ok, that's rhetorical. The point is that the web is different, and while we shouldn't settle for the limitations of the medium long term, we should embrace those constraints in the short term.
We should also take advantage of the strengths. Naturally, one of those strengths is the ability to use liquid layouts. Don't worry that your design may "fail" if somebody's screen is too big, that's the nature of the beast. What should concern you more is that fixed-width designs may be "failing" at larger screen resolutions.
Increased Resolutions
While it isn't super-prevalent yet, a quick glance at TheCounter.com and we can see that the 800x600 market share is continuing to shrink. And for anybody who's read about Longhorn, Microsoft is betting that by the time it is released, most everybody will be running 1024x768.
Ok, that's not saying much, but that's not a huge gap from 800x600. And I'm guessing that most designers are running somewhere in the neighborhood of 1280. Do you think that a stripe of a website down the center of a screen is creative? (Hint: It's not.) Ok, no more rhetorical questions, I promise.
Style Sheet Switching
It's not easy to create a liquid layout that works, and that's most likely the number one reason that more people haven't done it. Doug and Dan have nailed it in my opinion. They offer both fixed and liquid through the wonders of style sheet switching. It's not easy to mold the same content to fit both styles, but if they can do it, so can you.
Designers Desire Pixel-Precise Control
This is probably the most disappointing cause of fixed-width layouts. When it comes down to it, designers want, and are accustomed, to control every pixel and font to make their design perfect. This is frustrating enough with CSS and XHTML, but when you tell a traditional designer that different browsers will interpret their code differently, that different screen resolutions might leave too much white space, or, God forbid, not everybody has that font installed on their machine, they aren't going to like it.
They come from a world of control and precision, and these variables just aren't acceptable to them. Someday web development may provide that kind of control. In the meantime though, it doesn't, and if you can't let that go at least a little bit, you shouldn't be designing for the web.
Then why used fixed?
Fixed layouts aren't all bad. They're easier to create. They provide more precise control. They can also help you use optimal line length, a point that should not be taken lightly. Hell, all of my sites are fixed-width.
As with anything, there is no definitive answer, and everybody needs to decide for themselves and their situation. But next time you are deciding, give liquid a chance. Doug and Dan did, and I'm willing to bet you respect their work.
Also, since somebody is bound to point it out, this site isn't liquid. I'm the pot, and yeah, I'm calling the kettle black. I took the easy way out, and I admit it. I did, however, spend a lot of time exploring and trying liquid layouts for this site. Sadly, it didn't work for me. I'm probably just not good enough, but I know the rest of you are.

Comments are closed.
I do pretty much all fixed width as well. While its nice to talk about freeing your design and all that, I often don't have the time to trouble shoot a liquid layout on every screen size in every browser on every platform--and if I did, the benefits likely wouldn't outweigh the cost. Am I really concerned about the white space on the sides of a site on a 1600x monitor? No, not really. They're used to it :)
Speaking of 1600x monitors, text columns on liquid layouts can get REALLY wide there--much too wide really. 500px is about as wide as I'd ever want a text column. So until IE starts supporting min and max width values in CSS, I'm going to stick with fixed widths.
One last thought--concerns with high res screens assume the user has the browser maximized. I use dual 1280x screens, and rarely maximize my browser. Sites are built for smaller resolutions, so there's simply no reason to maximize it normally, unless I'm going over large graphic files or really long pages.
All very good points. And you hit a point that I completely forgot to mention. Good min- and max-width suppor will make a huge difference in the number of people implementing liquid designs. I might be in the minority, but I almost always try to maximize my browser, but I'm ususally rolling on 1280 screns.
I run at 1600x1200 and guess what? a fixed width sitting in the middle doesn't bother me in the least. Aligned to the left I find myself craning my neck to the left. And liquid designs have such long line lengths that I end up resizing my browser down to minimize the impact.
to me, a max-width or fixed-width layout aligned in the middle is the best layout. (I should probably follow my own advice. :^D)
I agree that there is no real reason against using fixed layouts. Its to the good structure of the markup to make a site accessible. And if there's no real support of min or max-width (without using java-script tricks) we will allways run in problems with line-length or design issues like header-graphics widths.
I definitely wasn't implying that a a small site down the middle of a large screen would bother anyone. I just think that the real estate could be used better for those individuals. There's always room for improvement.
I have a 17" monitor with a resolution of 1280x1024. My smallest font size is 17 because I don't want to use a microscope to read a website.
The white space is ok, but the fixed font and box sizes are totally messed up. Texts are overlapping each other and are cut at box edges.
For an example change your minimum font size to 18 and surf to RTL.
Defnitely worth bringing to the discussion:
ManInBlue: Resolution dependent layout
A flexible layout that automatically switches stylesheets dependent on screen resolution (uses Javascript)
It's interesting to note that recently, a high profile e-commerce site, Newegg.com, has been testing their new site design in "Beta" form at http://www2.newegg.com which initially had a fixed-width design (800px). After about a month or so of testing and user feedback (they are one of the Top 1000 websites according to Hitwise and Alexa), they pulled the site down and now it's back up with a liquid width setup that fills the the resolution.
However, since they have a large area for products in the center section, having a liquid design allows users with higher resolutions to take advantage of displaying more products per row and effectively reduce the amount of scrolling needed.
Garett, I guess that this article and the discussion about this post might be interesting for you...