* Magnus Kristiansen wrote:
Mouseover/out events will trigger when elements contained inside the
EventTarget are hovered, and then bubble up. This is contrary to the most
obvious interpretation, as you are still inside (over) the targeted
element. IE supports two events, mouseenter[1] and
be
ignored. Returning false from the handler does not help.
Chris
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ian Hickson
Sent: Thursday, May 08, 2008 2:56 AM
To: Magnus Kristiansen
Cc: [EMAIL PROTECTED]
Subject: Re: [whatwg] Adding mouseenter
On Thu, 15 Mar 2007, Magnus Kristiansen wrote:
Mouseover/out events will trigger when elements contained inside the
EventTarget are hovered, and then bubble up. This is contrary to the most
obvious interpretation, as you are still inside (over) the targeted element.
IE supports two events,
2007/3/16, Gareth Hay [EMAIL PROTECTED]:
Well, the current W3C spec has relatedTarget specifically for these
use cases, so again I fail to see why adding convenient shorthand for
functionality is a good thing here.
If we try to cover everyone's use cases with easy functionality, the
spec is
Is one of the objectives here not to repeat the same mistakes as in
the past?
Anyway, I seem to be the only descenting voice on this topic, so I
suppose I should yield.
On 16 Mar 2007, at 09:31, Martijn wrote:
2007/3/16, Gareth Hay [EMAIL PROTECTED]:
If we try to cover everyone's use
2007/3/16, Gareth Hay [EMAIL PROTECTED]:
Is one of the objectives here not to repeat the same mistakes as in the
past?
What do you mean? Which mistakes?
Regards,
Martijn
Well, this is my final word on the subject, it's my opinion, and by
the looks of it, only my opinion, but I *personally* don't see the
need for changing what we have.
I believe that all use cases are currently covered by the W3C spec.I
think IMHO that adding 'shorthand' functions, for
On Fri, 16 Mar 2007 11:35:57 +0100, Gareth Hay [EMAIL PROTECTED] wrote:
For instance, if you had a 'branding' image for your web sites, and it
is always 100px x 100px, that is not good for you to have a new
attribute on the img tag for 'branding', so that the image is always
rendered
Gareth Hay wrote:
Maybe your use case requires something different, but I can't imagine
that scenario.
I ran across this issue the other day, and found this explanation /
example which may help clarify the issues people encounter:
http://dynamic-tools.net/toolbox/isMouseLeaveOrEnter/
Rob
It's not a case of not understanding. I fully understand the use case
and bubbling, I just don't see this as a problem.
On 16 Mar 2007, at 12:29, Rob Crowther wrote:
Gareth Hay wrote:
Maybe your use case requires something different, but I can't
imagine that scenario.
I ran across this
On Thu, 15 Mar 2007 02:02:46 +0100, Gareth Hay [EMAIL PROTECTED] wrote:
On 15 Mar 2007, at 00:30, Magnus Kristiansen wrote:
Mouseover/out events will trigger when elements contained inside the
EventTarget are hovered, and then bubble up. This is contrary to the
most obvious interpretation,
I'm not so sure it is a workaround though.
If you know that the event will bubble, you can make your handler
prevent bubbling.
I don't think we should be adding two new events to a spec, when the
existing events can work in the way you want, albeit with a line more
code. If we did, we'd
On Thu, 15 Mar 2007 20:10:33 +0100, Gareth Hay [EMAIL PROTECTED] wrote:
I'm not so sure it is a workaround though.
If you know that the event will bubble, you can make your handler
prevent bubbling.
I don't think we should be adding two new events to a spec, when the
existing events can
2007/3/15, Magnus Kristiansen [EMAIL PROTECTED]:
On Thu, 15 Mar 2007 20:10:33 +0100, Gareth Hay [EMAIL PROTECTED] wrote:
I'm not so sure it is a workaround though.
If you know that the event will bubble, you can make your handler
prevent bubbling.
I don't think we should be adding two new
I think I am clearly missing something.
If we take your example, a parent element and several child elements.
If you want to perform an action on mouseover of a child - attach
the event there and cancel bubble.
If you want to perform an action on parent mouseover - attach to
parent element
Mouseover/out events will trigger when elements contained inside the
EventTarget are hovered, and then bubble up. This is contrary to the most
obvious interpretation, as you are still inside (over) the targeted
element. IE supports two events, mouseenter[1] and mouseleave[2], which
solve
Can't you just return false from an event handler to prevent further
bubbling?
On 15 Mar 2007, at 00:30, Magnus Kristiansen wrote:
Mouseover/out events will trigger when elements contained inside
the EventTarget are hovered, and then bubble up. This is contrary
to the most obvious
17 matches
Mail list logo
