Eric A. Meyer wrote:
> At 2:23 PM +0000 12/1/05, Tony Crockford wrote:
>
>> this sounds a bit strange but why are you doing #tabs.ski which means
>> id=tabs.ski
>
> That's not quite right. To select the following:
>
> <div id="tabs.ski">...</div>
Yeah, I spotted my idiocy within seconds of pressing send but my
emails took two agonising hours to reach the list...
something that has since occurred to me though is, that in the example
originally posted there are two divs each with ID="tabs" but with
different classes. Which, surely, *is* invalid code - ID needing to
be unique on the page and all, in which case I don't see a benefit to
using the ID.Class notation ?
why would you use id.class on an element (apart from the fact that it
doesn't work in IE) when giving a page element an id (consistent
throughout the site but unique per page - e.g footer) and adding a
class (declared by element in the stylesheet) works just as well.
e.g
on one page:
<div id="footer">
<p>some text</p>
</div>
on another page
<div id="footer" class="fancyfooter">
<p>some different text</p>
</div>
;o)
______________________________________________________________________
css-discuss [EMAIL PROTECTED]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
