I see. Good to know. Let's let this thread die and stay on the other
one. I sent you a reply in that one.
On Nov 1, 1:51 pm, Karl Swedberg wrote:
> On Nov 1, 2009, at 1:49 PM, jmatthews wrote:
>
> > On the topic of mouseenter and mouseleave, which some of you
> > recommended, quirksmode says on
On Nov 1, 2009, at 1:49 PM, jmatthews wrote:
On the topic of mouseenter and mouseleave, which some of you
recommended, quirksmode says only IE supports this method, and the
others do not at this time. The quirksmode sponsor is very critical
of their failure to incorporate these methods because
On the topic of mouseenter and mouseleave, which some of you
recommended, quirksmode says only IE supports this method, and the
others do not at this time. The quirksmode sponsor is very critical
of their failure to incorporate these methods because it would make
the coding far less complex.
So,
On the topic of mouseenter and mouseleave, which some of you
recommended, quirksmode says only IE supports this method, and the
others do not at this time. The quirksmode sponsor is very critical
of their failure to incorporate these methods because it would make
the coding far less complex.
So,
On the topic of mouseenter and mouseleave, which some of you
recommended, quirksmode says only IE supports this method, and the
others do not at this time. The quirksmode sponsor is very critical
of their failure to incorporate these methods because it would make
the coding far less complex.
So,
Andrei, I think you've hit it!
I really don't quite understand the quirksmode material as well as you
veteran programmers, but I can tell this is the crux of the issue and
how to handle it. It has to do with handling fromElement and
relatedTarget.
Do you think you could assist with this in order
Andrei, I think you've hit it!
I really don't quite understand the quirksmode material as well as you
veteran programmers, but I can tell this is the crux of the issue and
how to handle it. It has to do with handling fromElement and
relatedTarget.
Do you think you could assist with this in order
Andrei, I think you've hit it!
I really don't quite understand the quirksmode material as well as you
veteran programmers, but I can tell this is the crux of the issue and
how to handle it. It has to do with handling fromElement and
relatedTarget.
Do you think you could assist with this in order
Andrei, I think you've hit it!
I really don't quite understand the quirksmode material as well as you
veteran programmers, but I can tell this is the crux of the issue and
how to handle it. It has to do with handling fromElement and
relatedTarget.
Do you think you could assist with this in order
Andrei, I think you've hit it!
I really don't quite understand the quirksmode material as well as you
veteran programmers, but I can tell this is the crux of the issue and
how to handle it. It has to do with handling fromElement and
relatedTarget.
Do you think you could assist with this in order
BTW, Andrei. Now that the map stuff loaded, the next time you load
the page, it should be pretty quick.
If not, let me know.
BTW, Andrei. Now that the map stuff loaded, the next time you load
the page, it should be pretty quick.
If not, let me know.
I understand where you come from. My exprimation was somewhat off.
Please replace with desired with *implemented* or
*the-way-it-actually-works-in-browsers*.
Not sure if it is intended or just the way it is working with now.
Please check the links from quirksmode for further details.
On Sun, Nov
BTW, Andrei. Now that the map stuff loaded, the next time you load
the page, it should be pretty quick.
If not, let me know.
On Nov 1, 10:54 am, Andrei Eftimie wrote:
> > Mousing over class="placemark" causes it to fire as if there was a
> > mouseover on class="Senate." "placemark" has its own class, separate
> > from the "senate" class.
>
> This behaviour is actually the way it supposed to be.
> mouseover and mouseo
> Mousing over class="placemark" causes it to fire as if there was a
> mouseover on class="Senate." "placemark" has its own class, separate
> from the "senate" class.
This behaviour is actually the way it supposed to be.
mouseover and mouseout fire on each entering / exiting of the elements
and e
I'm installing GE now, but it would be great if you could create a
sample test-page to highlight this particular behaviour.
(and exclude everything else from that page, for easier further testing).
On Sun, Nov 1, 2009 at 6:37 PM, jmatthews wrote:
> I tried that, too.
>
> This is some bizarre beha
I tried that, too.
This is some bizarre behavior. It is not at all what you would
predict.
Let me show you the Firebug-generated html tree below.
Senate
HOW DO I GET OUT OF THIS LIST? !
2009/11/1 Karl Swedberg
> I'd stick with what Scott said. Use mouseenter/mouseleave. But instead of
> setting the style with .css(), just add and remove a class. Here is a demo:
>
> http://jsbin.com/enero/edit
>
>
> --Karl
>
>
> Karl Swedberg
> www.e
I'd stick with what Scott said. Use mouseenter/mouseleave. But instead
of setting the style with .css(), just add and remove a class. Here is
a demo:
http://jsbin.com/enero/edit
--Karl
Karl Swedberg
www.englishrules.com
www.learningjquery.com
On Oct 30, 2009, at 4:26 PM, jm
I tried them as the description in the reference was not clear as to
why it would be useful.
It doesn't solve the problem. That it does is make sure that if you
reached the child by entering over the parent, the child event will be
released only by exiting back over the parent.
Kind of odd.
On Oct 30, 9:30 am, jmatthews wrote:
> When I mouseover a child, it is thinking it is just the contents of
> parent. I need to restrict mouseover to children only, regardless of
> the fact that they are encapsulated by parent.
You might want to look at the mouseenter and mouseleave events.
Okay. The problem is now this:
The children are wholly contained within individual divs encapsulated
by parent, as follows:
state
child
When I mouseover a child, it is thinking it is just the contents of
parent. I need to restrict mouseover to children only, regardless of
the fact th
Thanks, I tried it. It turns out that !important gives precedence to a
property that has been later trumped by a more proximate designation.
In my app., ".placemark" will be a class of items below state with
id="AL."
I was able to control it in CSS to where ONLY the parent's attributes
do not app
24 matches
Mail list logo
