I've already explained twice that the workaround method was deprecated, not the element. Apparently the term "deprecated" sets off warning bells in everyone.

I know you can do regular rollovers in CSS; that wasn't what I asked. I meant hovering over one image (note, an IMAGE, not a little coloured region with an ugly little bit of arial in it) and causing several other images to change at once. I'll just look around a bit more and see if I can find something in CSS that isn't bland.

EDIT: OK, this looks pretty decent, although still good old reliable columns:
http://deepblue.indika.net.id/

CSS is only as bland as the designer.

(tee hee)


Man, I haven't read Malay/Indonesian for a while.

I think this site has some cool stuff.

http://veerle.duoh.com/index.php

The point for using DIVs instead of tables is semantic code. A table is for TABULAR data. A layout is not tabular data. A DIV is for grouping elements.

And if you are trying to pretend that DIVs are tables when coding a CSS layout, you're doing it wrong. You don't need to pretend DIVs are tables, but blocks of elements. As you said, all the web elements have it's place; you just need to use them for the right things.

And the whole reason for using CSS as much as you can instead of tables/javascript or anything else you can think of is mere accessibility. It loads faster, it's semantic and withouth CSS, chances are that it will still work.

I know that tables are for tabular data. It's what they were originally used for. However, it's also a nice way of structuring things. HTML without tables is too simple on the other hand, although tables weren't used in the early days for website layouts.

I didn't say anything about pretending that divs are tables. I said that you have to pretend that there (not they're) are tables, but instead you're using divs and margins. This is for alignment, positioning, etc. In the same way as you can see content inside of a td tag on the left side or on the right side, you have to know the locations of where you're placing things. That's all I was saying.

Accessibility or quick loading isn't always what makes a good website though, but I understand what you're saying.

Veerle's blog is great. I found it earlier this year in a web design magazine I was browsing through. I think he uses ExpressionEngine or something for his blog.

removed dead link