Description Ian Tewksbury 2010-10-28 15:08:58 EDT

Both JSDTHyperlinkDetector and JavaElementHyperlinkDetector take upwards of 3 seconds to return a result when the JavaScript type hierarchy is large.  This is due to a grander problem with building the JavaScript type hierarchy that has yet to be solved.  The problem is in the case of these detectors is that they are registered on the CTRL key by default and the CTRL key is also used for copy past operations.  Thus when a user selects an area of JavaScript and then presses the CTRL key to invoke a copy the JSDT hyperlink detector will be activated.  In the case of project with large JavaScript type hierarchy this causes an apparent freeze to the user while the detector calculates all for not because the user is just trying to do a copy.

The end result here is to the user Eclipse will freeze for upwards of 3 seconds when invoking a copy operation using the CTRL+c keyboard shortcut.  This side affect justifies an immediate response, more immediate then addressing the over arching issue of JS type hierarchy performance.

The suggested fix for this is to updated the JSDT hyperlink detectors to only calculate links if the user has not selected an area (like they would during a copy operation).