I thought I should pick up on the comment by Peter and ask one of my many newbie questions... What is the advantage of the fact that IDs must be unique on a page? I am aware of the circumstance that if you need to "repeat" an ID, set is as a class, but have still not figured out the advantage of an ID.
If you used absolute positioning, or a background image of the company branding, or a structure only appropriate for the main navigation, or some other set of styles that should only be rendered if they are unique on the, then it is useful to have IDs instead of classes. In today's browsers, put multiple IDs on a page and the page is ok, if maybe unusually styled. But future browsers are likely to be more strict and may display a big fat parse error message for such a page. That's a good thing -- it'll help you identify when you accidentally gave two id="nav" styles to teh same page.
It will be problematic, however, when you combine templates, CMSs, and webservices-sourced XML all in one document. This is where we are rescued by namespaces and the increasingly common habit of giving IDs unique prefixes based on the author.
--
Ben Curtis : webwright
bivia : a personal web studio
http://www.bivia.com
v: (818) 507-6613****************************************************** The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help ******************************************************
