Ok. Now that's what you should have said at the beginning.
That's a little bit more involved, but it could be done.
You would need a container division for each row as well as the
columns. Such as .rowcontainer and .colcontainer.
When the mouseover activates for a chosen cell, the colors will be
generated by the statement itself.
Interesting idea, I'll play with that later.
At this point, I think it really makes more sense to mark up the table as a
plain table, attach mouseover and mouseout events to each cell, and use
scripting to do the highlighting (by setting style properties on groups of
cells using the DOM). The problem with the row and column container
proposals is that they require destroying the logical markup of the table
(e.g. converting an NxM table into M Nx1 tables) in order to achieve a nice
but optional effect. It's less harmful to use optional features (like
scripting) to achieve optional effects than to torture the data.
For example, if the table is properly marked up, someone might be able to
import it into an analytical application of some sort, and if an advanced
browser with special support for true tables were to appear, it could allow
resizing/rearranging columns, sorting rows, etc. But if the table's
structure has been destroyed for purely presentational reasons, that can't
happen.