> I don't know what you're trying to accomplish with this,
I am trying to update a div dynamically. In my application, it
replaces it with an async http request, but the net effect seems to be
the same in terms of IE.
> but you are
> overwriting the innerHTML of one node with that of another than contains an
> id declaration, so for one thing you no longer have unique ids in your DOM.
Ok, that's an error on my part. I updated the updater function to do this:
Element.update('draggercontainer',
$('otherdraggercontainer').innerHTML);
Element.remove('otherdraggercontainer');
> IE has different behavior than FF with respect to non-unique ids so this is
> probably your problem.. Anyway, using script tags inside of a div and
> calling Element.update with the innerHTML to recreate the draggable is not a
> good idea. You should rethink what you are trying to do exactly.. If you
> want to replace the innerHTML of a draggable without killing it, wrap the
> content in span and Element.update the span instead and your draggable will
> still work afterwards.
I think this is closer to the actual problem. It seems as if it's not
possible to add a new draggable in IE by dynamically updating an
element? I suppose I need to find a workaround, because my app
functions by replacing a whole series of draggables every now and
then.
> Also, in the future, please don't post attachments. Instead, put up a live
> page on your own server and post a link.
Oops, sorry. I have placed it here:
http://dedasys.com/dragdrop10_test.html
Here's something strange, though. When I use the .js files from here
to drive that page, I can complete the drag and drop of the blue
element.
http://script.aculo.us/playground/
I can't seem to drop the remaining div in that case, though.
However, if I switch over to using the latest .js files from
subversion, things go haywire much quicker. As soon as I'm done with
the drop, I can't even mouse over the page without getting errors.
I tried playing around with .destroy()ing the drag/dropped element and
a few other things, but none of them were successful on IE, and none
of them generated errors at all in Firefox.
Thanks for any insights,
--
David N. Welton
- http://www.dedasys.com/davidw/
Linux, Open Source Consulting
- http://www.dedasys.com/
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
