As far as I can tell it has something to do with the orders in which
callback events are called when one animation is started before
another animation on the same element has ended. What can be done to
solve this problem I don't know.
On Aug 28, 2:36 pm, Gordon <[EMAIL PROTECTED]> wrote:
> Has n
Has nobody else run into problems with events firing in unexpected
ways or in apparently the wrong order or too quickly? This problem is
proving a real frustration and i can't find any way around it. I
thought the flag setting approach was a sensible one to prevent
unwanted functioning of the ev
Anyone?
On Aug 24, 3:40 pm, Gordon <[EMAIL PROTECTED]> wrote:
> I had a look at hoverIntent, but while it does seem to make the
> problem occur less often it doesn't prevent it entirely.
>
> Here's an example that illustrates the problem I'm having (using hover
> instead of hoverIntent so that th
I had a look at hoverIntent, but while it does seem to make the
problem occur less often it doesn't prevent it entirely.
Here's an example that illustrates the problem I'm having (using hover
instead of hoverIntent so that the problem is more obvious)
http://www.w3.org/1999/xhtml"; xml:lang="en
On Aug 20, 6:25 pm, Gordon <[EMAIL PROTECTED]> wrote:
> My first attempt simply did an animate () on the hovered item and
> another one when it was unhovered. this produced the desired scaling
> effect, but it also ran into a few problems when the mouse was moved
> over several items in quick suc
5 matches
Mail list logo
