For what it's worth, I've had some bad luck with innerHTML is IE, which occurred in code somewhat similar to yours. (I was slapping innerHTML into a pre-existing element, in any case). Not sure if it's related or not, but it's a pretty simple bit of code to create a "div" wrapper that IE seemed to like a lot more...see here: http://jerod.jerodandangela.com/?p=5
By removing the innerHTML call from an existing DOM element, and replacing with "appendChild", IE seems to accept it. Perhaps something similar is happening here? Just a shot in the dark... -Jerod On 5/22/07, Dave Crane <[EMAIL PROTECTED]> wrote: > > > Hi Charles, > > On Tuesday 22 May 2007 14:36, Charles St-Pierre wrote: > > Hi Dave, and thank you for your time > > > > (sorry if I respond only today. Long weekend here in Montreal, Canada) > > > No worries. Long weekends are good for the soul. We have two of them in > May > here in the UK :) > > > > > I've been trailing a JS error that appears in IE 6 WinXP. > > > > > > What does the text of the error say? > > > > Line:686 > > Error: Object doesn't support this property or method > > > > And debug point to the "catch(e)" line I pointed to. > > > Well, that's a pretty generic message, even by IE's standards - not sure > what > to suggest there, unfortunately. Looking at dragdrop.js (v 1.7.0), around > line 685, there's some code inside a call to Array.each() that tries to > find > a handle on each element. Maybe worth peppering a few debugger; statements > around there to see if you can locate the problem? $(e).down(), for > example, > in line 687, will only get triggered if the handle option is set. > > > > > That is ok, tripple checked. However, you've given me things to work > > on. > > What I actualy do is add HTML string in the innerHTML of the UL, and > > re-run Sortable.create. Is there a better way? > > > Nope, that's the right way to do it - if you modify your container (other > than > by dragging and dropping), recreate the Sortable. IIRC, there's some nifty > clean-up code under the hood that will remove the old Sortable before > applying the new one, so you don't end up with multiple event handlers on > the > nodes that were already there. > > > > Nope. I use the Script Editor (bundled with >gulp< FrontPage, or with > Vis > > > Studio if you use it. The freebie versions of Vis Studio might have it > as > > > part of them, if you've got 300MB free disk space needs eating up. > > > > Thanks for the info, I'll check it out. > > -- > ---------------------- > Author > Ajax in Action http://manning.com/crane > Ajax in Practice http://manning.com/crane2 > Prototype & Scriptaculous in Action http://manning.com/crane3 > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
