JavaScript Debugger: FF3 and 1.2.0b3
4 views
Skip to first unread message
PJ
Jun 18, 2008, 7:22:42 PM6/18/08
to Firebug
I've just upgraded to FF3.0 release and Firebug 1.2.0b3 and have
noticed an issue with the JavaScript debugger and breakpoints not
being hit sometimes...
I have a website with ~10 external .JS files in which I put a
breakpoint on one function.
When I look at the breakpoints tab I will see "undefined" as the
function name, and then the name of the external .JS file.
I have also noticed that executable code is not marked in green as it
should be.
Unfortunately this behavior occurs ~90% of the time, and has made
Firebug JS debugging unusable.
noticed an issue with the JavaScript debugger and breakpoints not
being hit sometimes...
I have a website with ~10 external .JS files in which I put a
breakpoint on one function.
When I look at the breakpoints tab I will see "undefined" as the
function name, and then the name of the external .JS file.
I have also noticed that executable code is not marked in green as it
should be.
Unfortunately this behavior occurs ~90% of the time, and has made
Firebug JS debugging unusable.
Liz
Jun 19, 2008, 10:44:21 AM6/19/08
to Firebug
I'm having exactly the same problem. I'm working with OpenLayers
which has very many separate javascript files.
I'll have to work from Firefox 2 in the meantime, as Firebug has
become integral to my web development.
Liz
which has very many separate javascript files.
I'll have to work from Firefox 2 in the meantime, as Firebug has
become integral to my web development.
Liz
John J Barton
Jun 19, 2008, 11:43:52 AM6/19/08
to Firebug
Please add test cases to the issues list so these can be fixed.
http://code.google.com/p/fbug/issues/list
http://code.google.com/p/fbug/issues/list
georgeap
Jun 21, 2008, 5:50:28 PM6/21/08
to Firebug
I'm experiencing the exact same problem. I'm not able to set any
breakpoints with FF3 and 1.2.0b3. It's amazing how dependent I am on
Firebug - looking now to downgrade back to FF2. Thanks for all the
work.
On Jun 19, 11:43 am, John J Barton <johnjbar...@johnjbarton.com>
wrote:
> Please add test cases to the issues list so these can be fixed.http://code.google.com/p/fbug/issues/list
breakpoints with FF3 and 1.2.0b3. It's amazing how dependent I am on
Firebug - looking now to downgrade back to FF2. Thanks for all the
work.
On Jun 19, 11:43 am, John J Barton <johnjbar...@johnjbarton.com>
wrote:
> Please add test cases to the issues list so these can be fixed.http://code.google.com/p/fbug/issues/list
John J Barton
Jun 21, 2008, 6:23:34 PM6/21/08
to Firebug
Its amazing how dependent Firebug is on you! If you don't create test
cases that demo your problem, we can't fix them.
cases that demo your problem, we can't fix them.
John J Barton
Jun 21, 2008, 8:15:35 PM6/21/08
to Firebug
Do breakpoints work on the first time you load the page but not on
reloads?
reloads?
beaujo
Jun 22, 2008, 5:55:59 PM6/22/08
to Firebug
I have the same issue. The breakpoint is marked as undefined as soon
as it is created. The location indicated by the breakpoint is correct
though.
The execution never breaks not even the first time.
When there is a long list of files, the js list popup does not behave
as well as before. There is no scrollbar when the list is too long. To
navigate through the files, you have to use the arrow keys.
Something else I remarked is that in this list I also get a bunch of
eval(...) strings that come from the Extjs library file: Ext2.0 ext-
all-debug.js to be accurate.
To work around this issue, I tried to reduce the number of js files
that are loaded (concatenating my debug versions), but to no effect.
Note also that I load the files dynamically creating a script element
on the fly and setting the src attribute to enable parallel
downloading of the files. Not sure whether it impacts fb.
Chris
as it is created. The location indicated by the breakpoint is correct
though.
The execution never breaks not even the first time.
When there is a long list of files, the js list popup does not behave
as well as before. There is no scrollbar when the list is too long. To
navigate through the files, you have to use the arrow keys.
Something else I remarked is that in this list I also get a bunch of
eval(...) strings that come from the Extjs library file: Ext2.0 ext-
all-debug.js to be accurate.
To work around this issue, I tried to reduce the number of js files
that are loaded (concatenating my debug versions), but to no effect.
Note also that I load the files dynamically creating a script element
on the fly and setting the src attribute to enable parallel
downloading of the files. Not sure whether it impacts fb.
Chris
beaujo
Jun 22, 2008, 5:55:29 PM6/22/08
to Firebug
I have the same issue. The breakpoint is marked as undefined as soon
as it is created. The location indicated by the breakpoint is correct
though.
The execution never breaks not even the first time.
When there is a long list of files, the js list popup does not behave
as well as before. There is no scrollbar when the list is too long. To
navigate through the files, you have to use the arrow keys.
Something else I remarked is that in this list I also get a bunch of
eval(...) strings that come from the Extjs library file: Ext2.0 ext-
all-debug.js to be accurate.
To work around this issue, I tried to reduce the number of js files
that are loaded (concatenating my debug versions), but to no effect.
Note also that I load the files dynamically creating a script element
on the fly and setting the src attribute to enable parallel
downloading of the files. Not sure whether it impacts fb.
Chris
On Jun 21, 5:15 pm, John J Barton <johnjbar...@johnjbarton.com> wrote:
as it is created. The location indicated by the breakpoint is correct
though.
The execution never breaks not even the first time.
When there is a long list of files, the js list popup does not behave
as well as before. There is no scrollbar when the list is too long. To
navigate through the files, you have to use the arrow keys.
Something else I remarked is that in this list I also get a bunch of
eval(...) strings that come from the Extjs library file: Ext2.0 ext-
all-debug.js to be accurate.
To work around this issue, I tried to reduce the number of js files
that are loaded (concatenating my debug versions), but to no effect.
Note also that I load the files dynamically creating a script element
on the fly and setting the src attribute to enable parallel
downloading of the files. Not sure whether it impacts fb.
Chris
On Jun 21, 5:15 pm, John J Barton <johnjbar...@johnjbarton.com> wrote:
Rob B.
Jun 23, 2008, 8:17:41 AM6/23/08
to Firebug
I have the exact same problem running FF3 and FB 1.2b3. The script
file dropdown is unusable due to all the eval() statements showing up
from Ext.js library.
FWIW, FB is an amazing tool and I can't wait to get full functionality
back. Thanks for all the hard work! You are my heroes!
file dropdown is unusable due to all the eval() statements showing up
from Ext.js library.
FWIW, FB is an amazing tool and I can't wait to get full functionality
back. Thanks for all the hard work! You are my heroes!
John J Barton
Jun 23, 2008, 11:48:39 AM6/23/08
to Firebug
Just a reminder, the file list has incremental search which works very
well.
1.2b4 will allow eval and event scripts to be filtered out.
well.
1.2b4 will allow eval and event scripts to be filtered out.
KevinH
Jun 23, 2008, 2:32:59 PM6/23/08
to Firebug
It's going to be difficult to send in examples because it seems to
have to do with script size or number of scripts.
When I do a simple "Hello world" onload script, the breakpoint works
fine. But on our enterprise code with thousands of lines and multiple
js includes, no breakpoints work. They are just ignored.
have to do with script size or number of scripts.
When I do a simple "Hello world" onload script, the breakpoint works
fine. But on our enterprise code with thousands of lines and multiple
js includes, no breakpoints work. They are just ignored.
John J Barton
Jun 23, 2008, 2:42:03 PM6/23/08
to Firebug
Kevin, I think it unlikely that the number of scripts causes the
problem with breakpoints. Its more likely a problem with complexity,
you are hitting the debugger in some way that I don't. We need a test
case or we are stuck.
Do you see green numbers in your scripts?
If you set javascript.options.showInConsole true in about:config, do
you see any errors in FF->Tools->ErrorConsole?
problem with breakpoints. Its more likely a problem with complexity,
you are hitting the debugger in some way that I don't. We need a test
case or we are stuck.
Do you see green numbers in your scripts?
If you set javascript.options.showInConsole true in about:config, do
you see any errors in FF->Tools->ErrorConsole?
KevinH
Jul 3, 2008, 1:58:49 PM7/3/08
to Firebug
Sorry for the delay. Indeed, I see no green numbers in the problem
file, nor do I see any errors in the ErrorConsole. (Also, today I'm
using 1.2.0b4.)
It does seem to be the complexity is the problem. I just know it
worked for this same code (beautifully, I might add) in previous
Firebug versions.
I'll try to work on a test case. Unfortunately, I simply can't
provide our enterprise code for this.
Thanks and cheers -
On Jun 23, 11:42 am, John J Barton <johnjbar...@johnjbarton.com>
file, nor do I see any errors in the ErrorConsole. (Also, today I'm
using 1.2.0b4.)
It does seem to be the complexity is the problem. I just know it
worked for this same code (beautifully, I might add) in previous
Firebug versions.
I'll try to work on a test case. Unfortunately, I simply can't
provide our enterprise code for this.
Thanks and cheers -
On Jun 23, 11:42 am, John J Barton <johnjbar...@johnjbarton.com>
Reply all
Reply to author
Forward
0 new messages