Drake, Ted C. wrote:
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.
...
I think this is the first time we actually disagreed on something!
Not necessarily disagreeing. Of course, if utter flexibility is the key (i.e. maybe need to add something else later), then yes by all means wrap things up. My comment was mainly aimed at situations in which there is no change planned in future, i.e. (to get back to my example) you will only ever have that one unordered navigation list. In that case, wrapping an additional wrapper around the list is a waste of bandwidth.
Of course, every real life situation is different. That's why it's difficult to just give absolute rules like "never use a div around a ul" or similar...it always depends on the actual circumstances (which is partly what may frustrate some people who are looking for dogmatic rules).
:) -- 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 ******************************************************
