Hi Patrick
Here's why I would continue to use div id="navigation" on a large web site.
There are situations that could require a subsection to be inserted below
the navigation. Having a div container allows you to insert elements in the
container, below the nav list.

This would be especially important on very large sites where you have
multiple divisions or products. The department may need to put an additional
contact box below the nav. Assuming the nav div is actually more of a side
bar. Of course, it would be better described as <div id="sidebar">. I guess
my point is: will the nav div ever contain more than that one unordered
list? If so, use the div. If not, apply the styles to the unordered list.

Once again, this is where experience leads.

I guess this is one of those instances where you need to strike the balance.

Also, let's say you want to give the navigation a rounded top and make it
fluid. You could apply the top right corner to the div and the top left
corner to the ul.

This is what makes me cringe

<div class="row">
<p> blah</p>
</div>
<div class="row">
<p> blah</p>
</div>
<div class="row">
<p> blah</p>
</div>

div.row {border-top:1px solid #333; margin-top:10px;}

I actually just saw a page like this on our server only the paragraphs were
one row tables!

I need two cups of coffee to hit that file.

I think this is the first time we actually disagreed on something!  

Ted




-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Patrick H. Lauke
Sent: Wednesday, September 07, 2005 11:33 AM
To: [email protected]
Subject: Re: [WSG] divitis - chronic vs. mild stages

Drake, Ted C. wrote:

> Now, the goal of a medium to advanced CSS-based programmer is to find the
> elegant balance of essential divs, spans, ids and classes. Consider it a
> challenge. 

Indeedy. I cringe, however, when I see DIVs where they're not necessary. 
For example things like

<div id="navigation">
     <ul>
         <li>...</li>
     </ul>
</div>

where a simple

<ul id="navigation">
     <li>...</li>
</ul>

will do.

That's the kind of stuff that should be avoided: if you already have a 
perfectly good block level element, don't wrap it in a generic div 
unless you have a very good reason for it.

-- 
Patrick H. Lauke
__________________________________________________________
re*dux (adj.): brought back; returned. used postpositively
[latin : re-, re- + dux, leader; see duke.]
www.splintered.co.uk | www.photographia.co.uk
http://redux.deviantart.com
__________________________________________________________
Web Standards Project (WaSP) Accessibility Task Force
http://webstandards.org/
__________________________________________________________
******************************************************
The discussion list for  http://webstandardsgroup.org/

 See http://webstandardsgroup.org/mail/guidelines.cfm
 for some hints on posting to the list & getting help
******************************************************
******************************************************
The discussion list for  http://webstandardsgroup.org/

 See http://webstandardsgroup.org/mail/guidelines.cfm
 for some hints on posting to the list & getting help
******************************************************

Reply via email to