BTW you can use FBTrace > Tools > Save to File, then post the file to a bug report
http://code.google.com/p/fbug/issues/list Then we can read the trace back in to help you interpret it. jjb On Apr 12, 12:19 pm, Dave Harper <[email protected]> wrote: > Darn - in reviewing my above posting I forgot to mention the one thing > that I felt was most important. This time around with FBTrace active, > doing a reload of the page I still get a corrupted display of the > JavaScript. This was unlike 1.8b2 where when it was active I got a > good display of the JavaScript and it was only corrupted when the > FBTrace was off. So now if I can figure out how to get the logging > going again, maybe we'll have something we can look at. > > Dave -- 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.
