Issue Details (XML | Word | Printable)

Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Blocker Blocker
Assignee: Ed Burns
Reporter: driscoll
Votes: 1
Watchers: 0

If you were logged in you would be able to see more operations.

Specify behavior of h:outputText and h:inputText

Created: 08/Jul/09 03:43 PM   Updated: 09/Jun/11 08:54 AM   Resolved: 09/Jun/11 08:53 AM
Component/s: Components/Renderers
Affects Version/s: 2.0
Fix Version/s: 2.2

Time Tracking:
Original Estimate: Not Specified
Remaining Estimate: 0 minutes
Remaining Estimate - 0 minutes
Time Spent: 2 hours
Time Spent - 2 hours

File Attachments: 1. Text File diffs.txt (7 kB) 17/May/10 06:40 AM - Ed Burns


Operating System: All
Platform: All

Issuezilla Id: 585
Status Whiteboard:

cat1 renderkitdoc size_small importance_medium

Participants: driscoll, Ed Burns and rogerk

 Description  « Hide

The behavior of h:outputText and h:inputText for rendering children is currently

The RI behavior for outputText is odd - it renders the children first, then the
value of the tag.

After extensive discussion in the EG, there was a rough consensus that children
for outputText not be rendered. During the process of implementing the fix, I
discovered that inputText had a similar undesired behavior, and also changed
that to not be rendered.

I've marked this P1, since this is slated for inclusion in the very next MR of
JSF, and the RI has already changed behavior to not render children.

Ed Burns added a comment - 24/Sep/09 09:13 AM

Move to unscheduled target milestone

Ed Burns added a comment - 24/Nov/09 07:40 AM

Prepare to delete api subcomponent

rogerk added a comment - 05/Mar/10 07:56 AM


Ed Burns added a comment - 15/Mar/10 01:57 PM


Ed Burns added a comment - 15/Mar/10 01:59 PM

2.0 rev a

rogerk added a comment - 13/May/10 08:02 AM

The RI has added a configuration option to enable the rendering of children.
And, by default, the rendering of children should not be done.
Currently, the renderkit docs for text rendering say:

"This component is responsible for rendering its children."

I suppose we could add a clarification like:

"Implementations may choose to disable the rendering of children by default."

rogerk added a comment - 14/May/10 09:03 AM


Ed Burns added a comment - 15/May/10 07:52 AM

These are valid 2.0 Rev a issues

Ed Burns added a comment - 17/May/10 06:38 AM
  • move to 2.1. When you do fix it, you can use this as the log message
  • modify javax.faces.{Output,Input} javax.faces.Text renderer to not
    render children by default, but do allow the possibility of a config
    option to control rendering.

About to attach patch.

Ed Burns added a comment - 17/May/10 06:40 AM

Created an attachment (id=232)
Fix for this bug, first iteration

rogerk added a comment - 23/Jun/10 07:45 AM


Ed Burns added a comment - 24/Jun/10 01:32 PM

Change target milestone.

rogerk added a comment - 27/Oct/10 12:57 PM


Ed Burns added a comment - 09/Jun/11 08:53 AM

Committed to trunk.

Sending jsf-api/doc/standard-html-renderkit-base.xml
Sending jsf-api/doc/standard-html-renderkit.xml
Sending jsf-api/src/main/java/javax/faces/context/
Sending jsf-api/src/main/java/javax/faces/webapp/
Sending jsf-api/src/main/resources/overview.html
Sending jsf-tools/src/main/resources/com/sun/faces/generate/facesdoc/stylesheet.css
Transmitting file data ......
Committed revision 9144.