Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 315278

Summary: [performance] JavaScript content assist times out after adding IE libraries
Product: [WebTools] JSDT Reporter: Chris Jaun <cmjaun>
Component: GeneralAssignee: Chris Jaun <cmjaun>
Status: RESOLVED FIXED QA Contact: Nitin Dahyabhai <thatnitind>
Severity: normal    
Priority: P3 Flags: thatnitind: review+
Version: 3.2   
Target Milestone: 3.2.1   
Hardware: PC   
OS: Windows XP   
Whiteboard:
Bug Depends on: 315277    
Bug Blocks:    
Attachments:
Description Flags
patch none

Description Chris Jaun CLA 2010-06-01 15:12:48 EDT 
+++ This bug was initially created as a clone of Bug #315277 +++

After adding the Internet Explorer library as a JavaScript runtime library, the JavaScript content assist will time out.

STEPS TO REPRODUCE
===============
o Create new project (Web Dynamic Project, Static Web Project, etc).
o Add/create test.js file.
o Open up test.js, and type document.g . On selection popup, select getElementById(elementId).
o Works great! No problem.
o Now, select your project. Right click then properties. Then, JavaScript>JavaScript Libraries.
o Select Libraries tab. Then click on Add Runtime Library.... Pick Internet Explorer Library.
o Now on your test.js, type document.g . On selection popup, select getElementById(elementId).. Your workspace should hang for at least 30 seconds. Then you get message box "Problems during content assist"
Comment 1 Chris Jaun CLA 2010-06-08 11:01:28 EDT 
Created attachment 171417 [details]
patch
Comment 2 Chris Jaun CLA 2010-06-22 15:44:04 EDT 
Fix checked into 3.2.1