I agree using CSS is good IF the thing you are hovering over is an <A> tag.
Many times you want to do something a little more complex, like hovering
over a <DIV> or <IMG> tag.
Also, the hover tag is useful to make hover on element A affect the look of
elementB.
$("p").hover(function(){
$(this).addClass("hover");
},function(){
$(this).removeClass("hover");
});
This gives a very flexible framework for all kinds of different hover
effects/options. The one I was calling overkill is defining onmouseover
functions and onmouseout functions.
Doesn't the above look much simpler that that?
Specifically, changing the img SRC attribute has the danger of flickering in
IE6. Using image-sprites and changing background-position or foreground
sprites that change absolute positioning reduce complexity of the image
management, reduce the http calls and eliminates the flicker.
Glen
On 9/6/07, Michael Stuhr <[EMAIL PROTECTED]> wrote:
>
>
> Glen Lipka schrieb:
> > This seems like massive overkill to me. What's wrong with the hover
> > function in the core API?
>
> and how would that look like ?
>
> as i already said: if you plan wisely i think all you need is css.
> just wanted to give an understandable example.
>
> micha
>
