Re: id bodyContent in documents not in news items

Geir BÊkholt wrote:
> Classes are not good enough. There needs to be one definitive ID that
> wraps the content of all content-types, really.
> This is necessary for scripts like the search-highlighter to work
> properly. I thought #content was good enough, but it actually
> (contradictory to its name) contains the add-item/state-menu.

why? .documentContent covers all content relevant stuff - we wanted to 
have a flexible (not only css wise, but structure wise) thing we can 
reuse for stuff that has repeating content blocks, like a blog index. we 
didn't see a reason for having a seperated class and id for the same 
purpose.

is looking up a single class slower than looking up an id? is looking up 
5 classes much slower than looking up one? as far as i've seen, even the 
external link js is pretty fast, even on old machines.

or am i wrong when i think you want an id for speed reasons?

> Please keep the DOM in mind and not just css when deciding what are
> classes and what are ids.

sorry we aren't js wizards ... but since we have a mailinglist, that 
gets discussed here anyway so such things won't fail again (this change 
was decided back when the nameageddon happend, on #plonedesign).

regards, michael
-- 
</gro.jiin//:ptth> °jiin


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click