Rails spinoffs - Dec 2006 - Problems with Drag & Drop in IE7

I''ve got some very simple drag & drop scripts that I''ve
put together
for testing purposes just so I can get the kinks worked out before I
build the drag & drop functionality into my application. The scripts
work fine in Firefox but when using IE7 it craps out after I drop a
draggable on a droppable.

I drag a username div to a number div drop it and the username reverts,
the ajax.updater works but when I go to grab another username div I get
an "unspecifed error" and none of my username divs are draggable.

I''m new to ajax and the scriptaculolus javascripts and would appreciate
any help.

I''ve got the scripts and the source up at
http://kristywienken.com/test/index.html.

Thanks,

Kristy


--~--~---------~--~----~------------~-------~--~----~
 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
rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-spinoffs?hl=en
-~----------~----~----~----~------~----~------~--~---

Hey Kristy,

Proper usage mandates that any droppable be explicitely unregistered
prior to its being removed from the DOM.

When using an Ajax.Updater over your <div id="numbers">, you end
up
replacing this div''s contents, hence the droppables in it.  You would
need to unregister all the droppables before that (using
Droppables.remove on each, probably from a onLoading hook in your
Ajax.Updater).

BTW, is it important that all your individual phone number zones be
droppables?  Or do you just need to be able to drop on numbers?  That
second option would work fine, since Ajax.Updater uses Element.update in
the end, which replaces the *contents* of your div, not the div itself.

Also, what is the purpose of your D''n''D here?  If
you''re trying to
provide dynamic list construction, maybe Sortable is more what you are
looking for.  It would just use Ajax.Request to notify the server side,
while updating the client-side directly w/o using a server-side-produced
full fragment.

''HTH

-- 
Christophe Porteneuve a.k.a. TDD
"[They] did not know it was impossible, so they did it." --Mark Twain
Email: tdd-x+CfDp/qHev2eFz/2MeuCQ@public.gmane.org

--~--~---------~--~----~------------~-------~--~----~
 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
rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-spinoffs?hl=en
-~----------~----~----~----~------~----~------~--~---