Specify behavior of h:outputText and h:inputText #585
Comments
Reported by driscoll |
@edburns said: |
@edburns said: |
rogerk said: |
@edburns said: |
@edburns said: |
rogerk said: "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 said: |
@edburns said: |
@edburns said:
About to attach patch. |
@edburns said: |
rogerk said: |
@edburns said: |
rogerk said: |
@edburns said: Sending jsf-api/doc/standard-html-renderkit-base.xml |
Marked as fixed on Thursday, June 9th 2011, 1:53:46 am |
@manfredriem said: |
This issue was imported from java.net JIRA JAVASERVERFACES_SPEC_PUBLIC-585 |
The behavior of h:outputText and h:inputText for rendering children is currently
unspecified.
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.
Environment
Operating System: All
Platform: All
Affected Versions
[2.0]
The text was updated successfully, but these errors were encountered: