On Aug 1, 5:50 am, Ken Snyder <[EMAIL PROTECTED]> wrote:
> jenner wrote:
> >> ...You _could_ call switchPositionsWithDOM() inside of
> >> switchPositionsWithMove(), but why on earth would you need the DOM order
> >> a certain way? DOM order is somewhat like an object properties--the
> >> object {a: 'first', b: 'second'} is effectively the same as {b:
> >> 'second', a: 'first'}. Maybe I'm missing something.
>
> > Actually, I'm just being lazy here - the DOM order is responsible for
> > the correct list member ordering (those DIVs contain form elements).
> > So after I've swapped the DIVs I'm "reindexing" all contained form
> > elements depending on their DOM order (s.th. like
> > container.getElementsBySelector('div.containing-divs-
> > class').each(<reassign indices for form elements here>);
> > ...
>
> So calling switchPositionsWithDOM() inside of switchPositionsWithMove()
> should work for this, or no?
Yeah, tried that already, looks a bit funny though, I guess I'll go
for the manual list member reindexing and forget the DOM stuff for the
moment.
On a totally unrelated note - for some reason element.relativize()
doesn't reset/remove the "top"/"left" styles from the element, any
ideas why?
Cheers,
jenner
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Spinoffs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/rubyonrails-spinoffs?hl=en
-~----------~----~----~----~------~----~------~--~---
