High Christoph, Yes, with high probability it is a FireBug issue, though I wanted to know if someone else recognized this, and if there is a workaround?
Thank you for your reply. -Zsolt On dec. 3, 20:27, Christoph Pojer <[email protected]> wrote: > I am not using Firefox or Firebug but in any case, this is a Firebug > issue and not a MooTools bug. > > On Dec 3, 8:15 pm, ZsZs <[email protected]> wrote: > > > > > Hi all, > > > Two days ago I installed Firebug 1.6 and from this this time I'm > > experiencing strange behavior in debugging. Now I tried to localize > > the problem: > > > <script type="text/javascript" src="../MooTools/mootools- > > core-1.3.js"></script> > > <script type="text/javascript" src="../MooTools/mootools- > > more-1.3.js"></script> > > > <script type="text/javascript" > > > function hello() { > > alert( "hello" ); > > } > > > hello(); > > </script> > > > The code above doesn't stops at any breakpoints. If I remove the > > mootools-more-1.3.js line, than FireBug works as usual. I'm curious if > > anyone experienced this strange behavior. I'm using FireFox 3.6.12 and > > FireBug 1.6 > > > - Zsolt
