Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 317641 - Cannot set style attribute for JSF HTML tags in XHTML files for Helios
Summary: Cannot set style attribute for JSF HTML tags in XHTML files for Helios
Status: RESOLVED WORKSFORME
Alias: None
Product: Java Server Faces
Classification: WebTools
Component: JSF Tools (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.3 M7   Edit
Assignee: Ian Trimble CLA
QA Contact:
URL: ORACLE_P1
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-22 16:31 EDT by Preston Appel CLA
Modified: 2011-03-21 15:52 EDT (History)
4 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 Preston Appel CLA 2010-06-22 16:31:00 EDT 
Build Identifier: I20100527-1700

The style attribute in JSF HTML tags in XHTML files cannot be set by the CSS Style Definition dialog.  The style attribute is inserted, if it didn't already exist, but it is given no value: style=""

This is happening on the Helios release for JSF 2.0 XHTML files.  This does NOT happen for JSP files in the same circumstances.

Reproducible: Always

Steps to Reproduce:
1. Create a dynamic web project with JSF 2.0 facet
2. Create a JSF XHTML file
3. Add an h:outputText tag to the file
4. Open the OSS Properties view/tab
5. Click on the style attribute editor button
6. Make style selections and click OK on the CSS Style Definition dialog
7. The text 'style=""' is written into the tag, but none of the style selections from the dialog.
Expected: Style selections from the CSS Style Definition dialog written into the style attribute, for example: style="font-style: italic"
Comment 1 Raghunathan Srinivasan CLA 2011-03-15 16:35:23 EDT 
Is this addressed by bug 221730 ?
Comment 2 Ian Trimble CLA 2011-03-21 15:52:44 EDT 
I'm not sure if it was the fix for bug 221730 that affected this, but something seems to have changed. I can't reproduce this. Please reopen with appropriate steps/observations/expectations if this shows up again.