John,
could you have a look if this change could fit in domManip() ?
callback.call( root(this[i], first), fragment.cloneNode(this.length
> 1 || i > 0) );
it seems solving the reported errors:
uncaught exception: Node cannot be inserted at the specified point
in the hierarchy (NS_ERROR_DOM_
An slightly slower but more robust solution would be:
eq: function( i ) {
return this.pushStack( this.get(i), 'eq', i )
}
The main difference is that the ret.selector would preserve the
initial index (relative if negative).
On Feb 28, 9:44 pm, Robert Katić wrote:
> If this solution seems
If this solution seems ok, I would update the ticket
http://dev.jquery.com/ticket/4188.
On Feb 28, 8:50 pm, ricardobeat wrote:
> Nice catch, that makes sense. Added it to the test page, it has no
> significant impact on performance.
>
> cheers,
> - ricardo
>
> On Feb 27, 7:27 pm, Robert Katić
Actually, that might not be too bad - we would just check to see if
one of the appending nodes exists in the set - and just not move it,
if that's the case. I'll check in to it.
--John
On Sat, Feb 28, 2009 at 3:20 PM, Dave Methvin wrote:
>
> This looks like a difficult one to fix:
>
> http://
We weren't currently using the check so I removed it. Thanks for the heads-up.
--John
On Sat, Feb 28, 2009 at 3:10 PM, Dave Methvin wrote:
>
> This has been a busy ticket:
>
> http://dev.jquery.com/ticket/4017
>
> I haven't see the problem myself, but you can tell by the activity
> that it's
This looks like a difficult one to fix:
http://dev.jquery.com/ticket/4087
In 1.3.x the selected nodes are moved out of the document before the
insert operation is performed. That means any inserts that depend on
the position of selected nodes won't work.
Ideas?
--~--~-~--~~
This has been a busy ticket:
http://dev.jquery.com/ticket/4017
I haven't see the problem myself, but you can tell by the activity
that it's causing some issues for IE users/developers. Down the ticket
a bit there's a proposed patch to add "text/plain" to the object tag,
but one person reported b
Nice catch, that makes sense. Added it to the test page, it has no
significant impact on performance.
cheers,
- ricardo
On Feb 27, 7:27 pm, Robert Katić wrote:
> Since .get(-1) will be supported, eq(-1) would be supported too (?).
>
> So your implementation needs some extra code:
>
> eq: functi
On Feb 26, 5:37 pm, chris thatcher
wrote:
> I get both sides, though I'm sure there are more than two ;) What I'm
> hoping is that we can keep jQuery simple, clean elegant (we could burden
> plugin developers just a little more to pass muster.) Let UI focus on
> widgets. And add a spot for the
The Flash trick could be interesting as well, put an object in position
absolute 0, 0 get the mouse position and remove it after
ExternalInterface.call("setMousePosition")
It's simple to implement, but eula problems plus flash plugin are too much,
imho, for a doubtfully useful task like this (onmo
last thing ... the onload could obviously be simply something like this:
attachEvent("onload", function(){
fireTheOnmouseOverEvent :-)
});
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"jQuery Development" group
>> Since the doScroll trick works over an interval, I am partially sure that
onmouseover will be fired alwasy before that interval.
tested right now, it is not true ... there is no way to predict who is
executed before but for sure the onmouseover event is fired only once while
the interval could
Hi Diego,
the onmouseover is activated as you said but only if the body is present.
Since the doScroll trick works over an interval, I am partially sure that
onmouseover will be fired alwasy before that interval.
document.documentElement.attachEvent("onmouseover", function(){
if(!arguments.cal
Having missed most of the discussion, I wanted to at least throw in
some existing resources on the topic.
For one, the Plugin Authoring guide covers a few of the requirements
that Matt listed: http://docs.jquery.com/Plugins/Authoring
On the topic of extending plugins, I covered one approach to t
14 matches
Mail list logo