Bug 114901 - Find doesn't work on Javascript files
Summary: Find doesn't work on Javascript files
Status: RESOLVED WONTFIX
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Webtools.WST.Javascript (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: David Williams CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-11-03 06:46 EST by Martin Lambert CLA
Modified: 2010-03-03 11:35 EST (History)
0 users

See Also:

Attachments
Example of reported problem (271.94 KB, image/jpeg)
2005-11-11 05:56 EST, Martin Lambert CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Lambert CLA 2005-11-03 06:46:47 EST 
1. Open Javascript file using Open Resource dialog
2. CTRL-F and enter a text string to search for (using one that does exist in
the file). 
3. Click the find button.

Rather than finding the text in question nothing "seems" to happen. Tested in
Java , Resource and J2EE perspectives. 

Find works correctly for other types of Resource such as Java classes.

I am using the M8 build of WTP on Eclipse 3.1.0
Comment 1 Nitin Dahyabhai CLA 2005-11-09 01:02:11 EST 
Is this happening consistently with multiple files?
Comment 2 Martin Lambert CLA 2005-11-11 05:56:31 EST 
Created attachment 29768 [details]
Example of reported problem
Comment 3 Martin Lambert CLA 2005-11-11 06:01:28 EST 
I chose a random Javascript file. I then copied a piece of text from the file
and used it in the search dialog.

In the given example I notice the search appears to have highlighted the method
entry point?
Comment 4 Nitin Dahyabhai CLA 2006-10-24 18:28:35 EDT 
It's working for me in 1.5.2.
Comment 5 David Williams CLA 2007-12-17 01:58:22 EST 
I'm doing a mass resolve of all open bugs in the wst.javascript component. 
Resolving to "won't fix". 

The reason is that the old wst.javascript component is being removed this release, and replaced by the wst.jsdt component. 

So ... if any owners of these wst.javascript bugs see the same problem in the wst.jsdt code, then please open a new bug on that component. 

Apologies we can't check each ourselves, but there's just too many (and too few people) so we'll need community help. Just glancing, I know for sure many will no longer be bugs but some may still be legitimate requests even in the new JSDT code.