Firebug 1.6a13

[John J Barton]

Mostly for the fix to issue 3017. Your comments on the preliminary
popup command line completion are welcomed.

http://blog.getfirebug.com/2010/06/21/firebug-1-6a13/
jjb

[skosman]

Not that I want to be the bearer of bad news, but the popup command
line "feature" caused me to roll back to 1.6a12 after all of 5 minutes
of usage. Any time I type in the console I get a popup window the full
height of my monitor, full of unselectable text, *that I can only
close by closing my entire browser window regardless of how many tabs
I have open.*

FF 3.6.3, OS X 10.5.8

[cheekybuddha]

I agree, the mechanism to make it diasppear as you continue to type
needs improvement!

skosman, the list will disappear if you hit Tab, but something will be
auto-completed in the command line.


hth,

d

[skosman]

Ah, didn't realize that Tab would close it (though the Autocomplete
will get in the way).

[NKjoep]

I'm using firefox 3.6.3 with ubuntu and firebug 1.6X.0a13.

I'm getting strange behaviour with the javascript
debugger and breakpoints with localfiles.

Sometimes firebug just doesn't apply the break
and ignores the breakpoints.

But happen a worse thing: firebug recognizes
there's a breakpoint and stop the script, then the
browser process starts eating all my cpu, so
the cpu usage goes to 100% and I have to kill firefox.

I have to switch back to the 1.6X.0a12 :) which works well.

--
Andrea

[John J Barton]

I need a testcase to fix this.
jjb

[Yun]

It works differently from the old firebug in which the command input
can be used. I command input is not shown. Strange behavior when
console tab is clicked.

m.y.

[Yun]

[NKjoep]

On Jun 23, 8:52 pm, John J Barton <johnjbar...@johnjbarton.com> wrote:
> I need a testcase to fix this.
> jjb

John I'm getting also problem to enable the script panel,
there's no specific page to test it, it just doesn't work
as expected to be :)

--
Andrea

[John J Barton]

Again, I don't know how to help you. I cannot see your screen, I
cannot see which keys or buttons you are pressing or what results you
are seeing. I don't know what you mean by command input or strange
behavior.

jjb

[John J Barton]

What operation are you performing and what happens when you do this
operation?

I guess you have some extension that we broke by changes in 1.6a13, so
we can't see what you are seeing unless we know what extension may be
involved.

jjb

[alexander....@googlemail.com]

I see exactly the same behavior. Two issues: it is triggered to fast /
unintended (space bar?) and it is hard to get it away (tab is not what
comes to my mind first, ESC is more like it).

Alex

[John J Barton]

We'll have a new version tomorrow.
jjb

On Jun 24, 8:05 am, "alexander.klimetsc...@googlemail.com"

[Christian Tölle]

Hi,

what do you think, wouldn't it be better if on an javascript error the
debugger hold on this line, an not reset the current callstack..
When I step trough code, and and error occurs.. Iam intrested in the other
variables around the error.... But now, theese vars are all gone cause the
callstack is reseted.. and the debugger goes on with the window.onmousemove
events etc...

Greetings

Christian

[John J Barton]

Please don't change the title of discussion threads.

If you have a new topic, create a new topic, thanks.
jjb