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

Bug 315277

Summary:

[performance] JavaScript content assist times out after adding IE libraries

Product:

[WebTools] JSDT

Reporter:

Chris Jaun <cmjaun>

Component:

General

Assignee:

Chris Jaun <cmjaun>

Status:

RESOLVED FIXED

QA Contact:

Nitin Dahyabhai <thatnitind>

Severity:

normal

Priority:

CC:

ccc

Version:

3.0.5

Flags:

thatnitind: review+

Target Milestone:

3.0.5 P

Hardware:

OS:

Windows XP

Whiteboard:

Bug Depends on:

Bug Blocks:

315278

Attachments:

Description	Flags
patch	none

Description Chris Jaun

2010-06-01 15:11:09 EDT

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

2010-06-01 15:12:34 EDT

Created attachment 170681 [details]
patch

Patch limits search scope when the token is "" to the current compUnit and its super types.

Comment 2 Nitin Dahyabhai

2010-06-01 23:16:53 EDT

Looks good.

Comment 3 Carl Anderson

2010-06-04 09:11:41 EDT

Committed to R3_0_5_patches