Diego, that patch makes the error go away because the selected node
now has a parentNode, but it's the wrong parentNode--it's the document
fragment instead of the original document. So, the element gets left
behind in the document fragment instead of being inserted back into
the document.
It loo
http://dev.jquery.com/ticket/4276
Clean-up some unused, orphaned code.
On Feb 13, 7:39 pm, "mike.helgeson" wrote:
> good stuff, thanks for taking it the rest of the way.
>
> -mike
>
> On Feb 13, 6:45 pm, Brandon Aaron wrote:
>
> > Very nice... all so quick too! :)
>
> > --
> > Brandon Aaron
>
I am working on a project and need URL param-parsing, as I usually do.
But this time I decided to try something new - based on ColdFusion
syntax that I have used for ages.
ColdFusion creates a system-level hash structure named "URL" that
contains all the URL params. This is very convenient, so I
Making "inline calling" would be avoided if not really necessary.
Is the speed difference of two solutions relevant at this point?
However, I am sure that John will consider this optimization too if
needed.
On Mar 1, 8:01 pm, ricardobeat wrote:
> We can preserve the index without resorting to g
We can preserve the index without resorting to get (and without
affecting performance) by using a ternary:
jQuery.fn.eq = function( i ) {
return this.pushStack( this[i<0 ? i+this.length : i], 'eq', i )
}
cheers,
- ricardo
On Feb 28, 8:42 pm, Robert Katić wrote:
> An slightly slower but mor
Because the query using the to selector path to resolve the element may be a
made at a much later time, in a different session, on a different machine
etc.
I simply need to build an efficient path to an element to be able to
retrieve the element at anytime in the future (assuming that the dom
struc
What's the value you see, within event.target ? (before the if).
--
Ariel Flesler
http://flesler.blogspot.com
On Mar 1, 12:47 am, Marc wrote:
> Firefox v3.0.6
> Firebug v1.3.3
> jQuery v1.3.1
> Windows XP sp2
>
> I've been troubleshooting a strange behavior with my script. While
> tracing throu
Firefox v3.0.6
Firebug v1.3.3
jQuery v1.3.1
Windows XP sp2
I've been troubleshooting a strange behavior with my script. While
tracing through the code I came across the fix() for jQuery.event. The
particular code in question:
-
if ( !event.target)
event.target = event.srcElement || document;
This is a FANTASTIC idea. We desperately need this sort of ability to
have multiple jquery versions co-exist. We are working on an
application that uses foxycart, which is currently locked into 1.2.6.
Meanwhile, because of a bugfix, we are locked into 1.3.2 or later.
Unfortunately both we and f
I realized after I made my last post (#57) I realized that you
described almost exactly what I had just built :). Sort of like
finding money behind the couch! Try:
http://code.google.com/p/jquery-plugin-dev/source/browse/trunk/jquery.plugin.js.
Anyways, I am not trying to say MVC is over-engineer
Hi guys,
I have written a couple of plugins that I'd to share. The first is an
MVC style mini-framework with the M and V (or C, depends on how you
look at it) stripped out of it. Anything more, IMHO, is overdoing it
no matter how large the project. It is called jFrame. It works on top
jQuery and
11 matches
Mail list logo
