Sorry, I should have mentioned that they are already being used _in
nightly builds_, exactly in the way you describe.
If this solution is to be chosen, I agree that this fact should be
documented.
The alternative implementation for bubbling submit/change/select
relies on click and keypress, for which the propagation is much more
likely to be stopped.
If there is a third way, I'd like to hear about it.

On Sep 21, 12:22 pm, Már <mar.orlygs...@gmail.com> wrote:
> > unlikely that anybody will use them in a modern Web page.
> > Our bubbling focus and blur are already relying on them.
>
> jQuery 1.3.2 doesn't seem to have bubbling focus and blur. Which
> library are you talking about?
>
> Given the current lack of bubbling of focus and blur events, focusin/
> focusout look extremely useful, (and are easily implemented as a
> plugin, using DOMFocusIn/Out and capture-phase blur/focus
> respectively).
> Mouseenter and mouseleave are also proprieatary microsoft events which
> happend to be exremely useful, and I don't see them beeing written off
> as "unlikely to be used" in existing, deployed code. :-)
>
> Secondly, focus and blur, vs. focusin and focusout have almost
> identical semantics which IMO makes .stopPropagation() bleed-over a
> lot less surprising, than bleed-over to other unrelated events such as
> submit, change and select.
>
> (Don't get me wrong, I'd love to see bubbling submit/change/select
> (and others), but if they come with the cost of seemingly arbitrary
> side-effects, they should at least come with a prominent warning in
> the documentation.)
>
> --
> Már
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"jQuery Development" group.
To post to this group, send email to jquery-dev@googlegroups.com
To unsubscribe from this group, send email to 
jquery-dev+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/jquery-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to