yeah i managed that with a check on element existence.
now it removes before appending, not appending before removing...
the problem was simple... the remove() itself was called in a
callback...
On May 15, 2:50 pm, "Erik Beeson" <[EMAIL PROTECTED]> wrote:
> Like I said before, when you call remove, execution won't continue
> until remove is finished. There's no need for a callback. Could you
> maybe clarify the problem that you are having? I don't understand what
> this means: "on appending a span to a div the previous span removes,
> but now the div jumps because of this". A simple test page that shows
> the problem would help.
>
> --Erik
>
> On 5/15/07, Equand <[EMAIL PROTECTED]> wrote:
>
>
>
> > On May 15, 1:58 pm, Sam Collett <[EMAIL PROTECTED]> wrote:
> > > Missed a line ($this.remove())
>
> > > On May 15, 11:10 am, Sam Collett <[EMAIL PROTECTED]> wrote:> You could
> > > save a reference to its parent before hand, e.g.
>
> > > > $("a.removeme").click(
> > > > function(e)
> > > > {
> > > > e.preventDefault();
> > > > var $this = $(this), $parent = $this.parent();
>
> > > $this.remove();
>
> > > > $parent.find(".removemetoo").remove();
> > > > }
> > > > )
> > this won't help... i don't need a function to remove...
> > i just need the next function to start right after the remove() but
> > not at the time of remove... so e.g. on appending a span to a div the
> > previous span removes, but now the div jumps because of this...
