On Apr 14, 10:21 am, Dave Harper <[email protected]> wrote: > On Apr 14, 2:27 am, "Honza (Jan Odvarko)" <[email protected]> wrote: > Good idea! I disabled all options and found that I did indeed see the > bad display after reloading my web page. Same thing with only ERRORS > enabled - nothing was logged and the display was incorrect. I have implemented a simple support for asynchronous displaying of the logs. (I believe that generating and rendering of the UI/HTML is what takes most of the time when a log message arrives to the console window).
It's disabled by default and in order to activate it you need to set extensions.firebug.fbtrace.layoutTimeout [ms] (0 by default) preference. If the value is >0 it represents number of milliseconds the console waits before rendering the log. If another message comes within this period the timeout is recreated and the console waits again. This also means that if the timeout is small and there is endless stream of logs they don't have to be displayed at all... You can install the extension directly from Firebug source, see some help here (description how to do it for Firebug itself) http://getfirebug.com/wiki/index.php/Firebug_Internals#Development_Setup But let me know if you prefer XPI and I'll release FBTrace 1.8b6 Honza -- 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.
