Chris Stratford wrote:
What is the advantage of an ID over simply giving something an ID??

No measurable advantage, but it's a question of principle and appropriateness: if something is unique (e.g. your page will only ever have one header, footer, main navigation bar, content area, etc), then ID is the most suitable attribute to use.


Sure, you could just use classes, or - at the other extreme - define lots of unique IDs like #item1, #item2, #item3 and then define something like #item1,#item2,#item3 { /* some CSS */ } and of course it would work...but it's really not following the idea behind ID and class.


-- 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

******************************************************
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