The whole browser freezes. FF CPU utilization is 0 and I can switch between FF windows. My guess is since mouse moves out of the ondrop scope and ondrop is not valid anymore this may be confusing Firebug. This is a very speculative at this point. I do not have time right now for a proper bug report, I hope I will be able to do it tonight. I will also try to upgrade Firebug to the same version as Chromebug and test again.
On Feb 3, 2:02 pm, John J Barton <[email protected]> wrote: > On Feb 3, 10:20 am, kirov <[email protected]> wrote: > > > I have drag and drop events. When the ondrop is triggered, Firebug > > correctly stops at a breakpoint, but then the browser stops responding > > and killing it is the only possible remedy. > > By "the browser stops responding" do you mean that the tab stops > responding (correct, it should be frozen on a breakpoint) or the whole > browser? > > > > > > > Here is the code: > > > ondrop="try { BioBrowser.dropSeqItem(event); event.stopPropagation(); > > event.preventDefault();} catch (err) { alert(err); }" > > > BioBrowser.dropSeqItem = function (event) { > > try { > > var listitem = event.dataTransfer.mozGetDataAt("application/x-moz- > > node", 0); > > var lb=event.target; > > lb.appendChild(listitem); > > return 1;} > > > catch (err) { > > alert(err); > > > } > > } > > A complete in a bug report would be useful. > > > > > I am using 3.5.7 on Win XP, Chromebug 1.6.0a3, Firebug 1.5. > > Please use the same version of Firebug as Chromebug, eg Firebug > 1.6.0a3 with Chromebug 1.6.0a3. > > jjb -- You received this message because you are subscribed to the Google Groups "Firebug" 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/firebug?hl=en.
