Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 339330 - No filter applied when trigger tag proposals in first child level of DOM Document
Summary: No filter applied when trigger tag proposals in first child level of DOM Docu...
Status: CLOSED DUPLICATE of bug 124946
Alias: None
Product: WTP Source Editing
Classification: WebTools
Component: jst.jsp (show other bugs)
Version: 3.2.2   Edit
Hardware: PC Windows Server 2003
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: jst.jsp CLA
QA Contact: Nick Sandonato CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-09 04:48 EST by Bin Ouyang CLA
Modified: 2011-03-09 13:32 EST (History)
2 users (show)

See Also:

Attachments
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 Bin Ouyang CLA 2011-03-09 04:48:39 EST 
Build Identifier: M20100909-0800

Proposals are not filtered by inputed complete/incomplete tag name if user trigger proposal at the beginning of a document in JSP Editor by CTRL+SPACE. The filter function works well if input a tag embedded in another tag.

Reproducible: Always

Steps to Reproduce:
1.New a jsp file by Jsp file wizard, and use JSP Template "New JSP File(html)".
2.Input "<jsp:att"at the beginning of editor.
3.Press CTRL+SPACE.
4.Proposal window shows up with all jsp tags proposal in this jsp file. Expected result is a filtered proposal list, which only contains the jsp:attribute proposal.
Comment 1 Carl Anderson CLA 2011-03-09 12:05:39 EST 
Bin, based on the build identifier, I am assuming that you are using Eclipse
3.6 SR1, which corresponds to WTP 3.2.2.  Have you tried 3.6 SR2 yet?
Comment 2 Nick Sandonato CLA 2011-03-09 13:32:54 EST 
Hi, Bin. Thanks for your report. This looks like the same inconsistent filtering problem reported by Bug 124946.

*** This bug has been marked as a duplicate of bug 124946 ***