The random numbers show up instantly when I do this, so it sounds like the speed problem *is* related to syntax highlighting.
https://code.google.com/p/fbug/issues/detail?id=7560 On Sunday, 22 June 2014 06:22:42 UTC+12, Simon Lindholm wrote: > > Could be either that or the syntax highlighting. A lazy way of testing > syntax highlighting performance is this: > 1. Go to about:config, turn on devtools.chrome.enabled > 2. Press Shift+F4 to open Scratchpad, and set it to Environment -> Browser > 3. Open Firebug on some page > 4. Run the following in Scratchpad: > > e = Firebug.currentContext.getPanel("script").scriptView.editor > st = e.setText > e.setText = function(s, type) { st.call(e, Math.random() + "", type); } > > and see how quick it is to switch between sources without actual script > texts having to be syntax highlighted and displayed. > > Den lördagen den 21:e juni 2014 kl. 01:23:49 UTC+2 skrev Sebastian Zartner: >> >> @Glenn: >> Wilfredo's problem was related to the HTML panel, not for the Script >> panel. >> The reason why switching works slower than before may be due to the >> change to an asynchronous fetching of the script sources instead of >> synchronously fetching them. (@Honza: please correct me if I'm wrong.) The >> advantage of this asynchronous workflow is that the Script panel doesn't >> block the rest of the browser UI anymore. This step was necessary to adopt >> the new JSD2 debugging engine >> <https://developer.mozilla.org/en-US/docs/Tools/Debugger-API> and get >> rid of the outdated and unmaintained JSD1 engine. >> The speed of switching between scripts may be improved, though. Please >> create >> an issue >> <https://code.google.com/p/fbug/issues/entry?template=User%20enhancement%20request> >> >> for that, so this request is not lost in the noise. >> >> Sebastian >> >> On Thursday, June 19, 2014 4:28:41 PM UTC-5, Glenn wrote: >>> >>> @Sebastian: I have a similar problem on Iceweasel 30 & FB 2.0. Since the >>> upgrade, the script panel is very laggy. Switching between scripts, for >>> instance, was instantaneous before, and now takes about 1s to switch. >>> Doesn't sound like much, but it's very annoying. Your suggestions don't >>> improve it. >>> >>> My guess is that it's something to do with the syntax highlighting, but >>> I don't see a way to turn it off to test. >>> >>> On Thursday, 19 June 2014 15:03:15 UTC+12, Sebastian Zartner wrote: >>>> >>>> @Wilfredo: >>>> I can't reproduce this on Win8.1 with Firefox 30.0 + Firebug 2.0 on a >>>> machine with AMD C-70 processor. >>>> What is "very slow" for you? Does it improve if you uncheck the HTML >>>> panel options >>>> <https://getfirebug.com/wiki/index.php/HTML_Panel#Options_Menu> *Expand >>>> Changes* and *Highlight Changes*? >>>> >>>> Sebastian >>>> >>>> On Friday, June 13, 2014 12:43:53 PM UTC-5, Wilfredo Porta wrote: >>>>> >>>>> I've been using Firebug 2.0, and is very slow. >>>>> >>>>> Try this: >>>>> >>>>> Inspect an element (textarea for example) and try changing the width >>>>> increasing it with the arrow keys from the css (HTML Panel - Styles). >>>>> Changing the size is very slow. >>>>> >>>>> Same behaviour with 1.12.8 >>>>> >>>>> Thanks. >>>>> >>>>> El martes, 10 de junio de 2014 09:16:08 UTC-6, Jan Honza Odvarko >>>>> escribió: >>>>>> >>>>>> https://blog.getfirebug.com/2014/06/10/firebug-2-0/ >>>>>> >>>>>> Honza >>>>>> >>>>> -- You received this message because you are subscribed to the Google Groups "Firebug" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/firebug. To view this discussion on the web visit https://groups.google.com/d/msgid/firebug/6c3be20f-aa95-47c4-a034-abf729c00b34%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
