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.
This appears to be a regression as it is working fine in NetBeans 8.1. I have tested this with an empty profile on the latest dev version and the issue is still present. When you Ctrl-Click on something that is in a different file NetBeans opens the file but no longer scrolls the page. The cursor is on the correct definition but the page has not scrolled to show it. Once you are in a file or if the method etc is in the same file then it behaves normally and scrolls correctly.
Could you please test it also in other languages like JavaScript and/or Java? Thanks.
I have tried this in a Java project and it appears to be OK but in a PHP project it is not :( My JavaScript projects are mainly node so they don't really have a lot of things to jump around to... I will try with something that has jQuery
Just tried in a JavaScript file and this appears to be happening in there too. So it happens for PHP and JS files but not for Java files
Thanks for your investigation! Reassigning to CSL, please evaluate. Thanks.
looks like https://netbeans.org/bugzilla/show_bug.cgi?id=258564
Yep these look like they could be the same thing...
Created attachment 159087 [details] only left pane is wrapped Still reproducible for HG in: Product Version: NetBeans IDE Dev (Build 20160401-276710bb7b4c) Java: 1.8.0_72; Java HotSpot(TM) 64-Bit Server VM 25.72-b15 Runtime: Java(TM) SE Runtime Environment 1.8.0_72-b15 System: SunOS version 5.11 running on amd64; UTF-8; en_US (nb) User directory: /export/home/vv159170/.netbeans/dev Cache directory: /tmp/nb_cache_dev
Interesting: if I use Tools->Diff to compare two files => both panes are not wrapped
Comment on attachment 159087 [details] only left pane is wrapped Sorry, it is for another issue
(In reply to Vladimir Voskresensky from comment #8) > Interesting: if I use Tools->Diff to compare two files => both panes are not > wrapped sorry, it is comment for another issue
This should be in fact dup of issue #258564 which is already fixed. *** This bug has been marked as a duplicate of bug 258564 ***