Nothing wrong with styling states with CSS, but there is plenty wrong
with using javascript to overwrite CSS states when you could do
exactly the same thing with CSS.
However, adding javascript to make a browser work like the others do
is fine, but you should try to compress it some what, to save
On 5/24/05, Thierry Koblentz [EMAIL PROTECTED] wrote:
It is said that flyout and dropdown menus belong to the behavior layer and
that CSS should not be used to accomplish such things.
Also, because this technique relies on CSS *and* Scripting it overlaps 2
layers; and that's supposed to be bad
On Tue, 2005-05-24 at 14:00 +0200, Michael Lykke wrote:
Im just wondering - Cause sometimes it seems to me that alot of effort
is put into making something correct way beyond just adhering to the
webstandards. Like asking whether it is ok to use list definitions
when the list only has a single
Rowan Lewis wrote:
Nothing wrong with styling states with CSS, but there is plenty wrong
with using javascript to overwrite CSS states when you could do
exactly the same thing with CSS.
However, adding javascript to make a browser work like the others do
is fine, but you should try to
I'm just saying that its silly to reinvent things like :hover with
javascript and DOM but its perfectly fine to write javascript to fix
browser incompatability (IE doesn't support :hover on all elements).
On 5/25/05, Thierry Koblentz [EMAIL PROTECTED] wrote:
Rowan Lewis wrote:
Nothing wrong
on your site is says
What's Bad
We're using CSS for another purpose than presentation.
why is it that bad?
On 5/24/05, Thierry Koblentz [EMAIL PROTECTED] wrote:
For people interested in à la suckerfish menus, this one now allows
tabbing navigation in MSIE too:
Frederic Fery wrote:
on your site is says
What's Bad
We're using CSS for another purpose than presentation.
why is it that bad?
It is said that flyout and dropdown menus belong to the behavior layer and
that CSS should not be used to accomplish such things.
Also, because this technique
