On Mon, 4 Jun 2007, Andrew Gaffney wrote: >> I seem to have made a school boy error a while ago and instead of >> using class's to define I used id's, thus having the effect of multiple >> id's with the same name in the same page. I can correct but wanted to >> know what damage multiple id's can do, regarding SEO etc. > > While it's not technically correct, afaik, it will only hurt anything if you > start using document.getElementByID() in javascript.
You cannot guarantee that, can you? For example, if an id value is used in a link (as fragment identifier), what will happen? Any CSS rule using an ambiguous id selector will have unpredictable effects, across browsers and years, even if you could somehow determine how current browsers treat it. The question is pointless. It's useless to ask how much doing things wrong will hurt you, when you can simply fix things - in this case, use class attributes and class selectors instead. -- Jukka "Yucca" Korpela, http://www.cs.tut.fi/~jkorpela/ ______________________________________________________________________ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d IE7 information -- http://css-discuss.incutio.com/?page=IE7 List wiki/FAQ -- http://css-discuss.incutio.com/ Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
