Bug 163021 - [jspcss] cannot specify expression language with Properties view for content type css jsp file.
Summary: [jspcss] cannot specify expression language with Properties view for content ...
Status: NEW
Alias: None
Product: WTP Source Editing
Classification: WebTools
Component: jst.jsp (show other bugs)
Version: 1.5   Edit
Hardware: PC Windows XP
: P2 enhancement (vote)
Target Milestone: ---   Edit
Assignee: jst.jsp CLA
QA Contact: Nick Sandonato CLA
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2006-10-31 21:16 EST by hoshiura CLA
Modified: 2013-07-18 14:26 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description hoshiura CLA 2006-10-31 21:16:24 EST
Properties view allows only valid css value. However, in content type css jsp, expression language is be used in general. 
I think you might need to give proper/valid primitive type to the CSS node.

One more thing, 
you need to delete JSPedCSSPropertySource.setPropertyValue() method after this feature is supported. In the method, expression language is rejected to avoid DOMException. DOMException happens in CSSPrimitiveValueImpl.setStringValue() method if specified value does not have valid primitive type.

*How to setup
1. Start workbench.
2. Create a web project.
3. Create a content type CSS JSP file.
4. Set the jsp file as CSS JSP content type with "General - Content Types" Preference page.
5. Open it with CSS JSP Editor and add a CSS declaration like below.
.selectorName {
 background-color: blue;
}
6. Edit CSS property value with Properties view.
--> If you specify ${aaa}, warning dialog appears. This is correct behavior at wtp 1.5.2. However, expression language should be inserted with future release if possible.
Comment 1 David Williams CLA 2007-01-06 00:53:38 EST
I'm going to classify this as an enhancement request, but that doesn't really change it's importance. It's just to signify "new function" as opposed to literally a defect as currently designed. Let me know if you disagree (or .. just change it back :)