This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
1. Create a web application with JSF framework. 2. Add a JavaScript file with 2 functions one of which is invoked from another. 3. Add first breakpoint to the first function before call of the second function. 4. Add second breakpoint in the beginning of the second function. 5. Debug application and do the action, which suspends debugger on the first breakpoint. 6. Press F8 to step over until call of the second function. 7. Press F7 to step into the second function. 8. When debugger on the line with breakpoint press F8 to step over or Ctrl + F7 to step out. Result: Debugger is still on the same line. If there is no breakpoint everything is fine, but with breakpoint debugger doesn't perform a command, user have to call this command twice, in spite of fact that debugger has already suspended one time on the line with breakpoint.
Created attachment 70614 [details] Screenshot of example JavaScript file.
This appears to be a Firebug issue. The key parts are stepping into a function and also having a breakpoint on the first line of said function. See: http://code.google.com/p/fbug/issues/detail?id=1179&sort=-id
In case of IE, the debugger will suspend on each statement not line when you step. Did you have multiple statements in the line where in you had to step twice. If not, please give me the exact line numbers where you had breakpoint and where you had to step twice. I have your webapplication2 project which you had attached for a different bug
I have only one statement per line. You can see this on screenshot. And it doesn't matter what line, you also can see on screenshot that debugger suspends on line "var y = 2;", but I also tried on line "var x = 1;" and had the same result.
As I mentioned earlier, this is a Firefox-only issue due to a problem in Firebug. See the Firebug issue that I linked.
This is dependent on Firebug. It does not appear that this issue has been fixed by Firebug yet, and there is no time line for resolving this issue.