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.

Bug 223961 - Differences in Step Into between embedded browser and Chrome
Summary: Differences in Step Into between embedded browser and Chrome
Status: NEW
Alias: None
Product: javascript
Classification: Unclassified
Component: Debugger (show other bugs)
Version: 7.3
Hardware: PC Linux
: P3 normal (vote)
Assignee: Martin Entlicher
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-12-18 08:10 UTC by Vladimir Riha
Modified: 2013-01-08 16:34 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Vladimir Riha 2012-12-18 08:10:10 UTC
I'm not sure if there is a way to resolve this, but it could be a bit confusing. Imagine following JS line with line breakpoint on it:

 console.log("======================="); // line breakpoint here
 test();

Now if code execution stops there and you press Step Into (F7), then:

- in Chrome, it continues to the line with test() call
- in embedded browser, it stops "somewhere", callstack says "wrapObject" line 68 so you actually stepping into somewhere, but in IDE, there is no visual indication other than different callstack and continue button being enabled. But the line stays red, although it should probably be as light purple (as for call stack lines).

Would it be possible to add some kind of fallback, in case code execution stops somewhere and the file cannot be opened, then the current line won't be red, but purple to indicate call stack from here?



Product Version: NetBeans IDE Dev (Build web-main-9550-on-20121218)
Java: 1.7.0_10; Java HotSpot(TM) 64-Bit Server VM 23.6-b04
Runtime: Java(TM) SE Runtime Environment 1.7.0_10-b18
System: Windows 8 version 6.2 running on amd64; Cp1252; en_US (nb)
Comment 1 Martin Entlicher 2013-01-08 16:34:21 UTC
Reproduced.
We should implement something like smart-stepping in Java debugger.
Step Out gets you back from the hidden code.