[
https://issues.apache.org/jira/browse/MYFACES-702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13180802#comment-13180802
]
Krashan Brahmanjara commented on MYFACES-702:
---------------------------------------------
>this issue should be fixed on 1.2.x and 2.0.x branches
So? Why you mark it as fixed without any changes.
Some corporate portals still use jsf 1.1 and old portlet bridge so they can't
upgrade theirs portals without this fix.
> outputText generates wrapped span element in a portal
> -----------------------------------------------------
>
> Key: MYFACES-702
> URL: https://issues.apache.org/jira/browse/MYFACES-702
> Project: MyFaces Core
> Issue Type: Bug
> Components: General
> Affects Versions: 1.1.0
> Reporter: Gavin Cornwell
> Assignee: Martin Marinschek
> Fix For: 1.1.2
>
> Attachments: myfaces702.patch
>
>
> We have a JSF app that runs as a portlet and normal webapp.
> In the webapp the <h:outputText value="some text"/> appears as I would expect
> (i.e. just the text) however the same thing in the portlet gets rendered as:
> <span id="form-id:handleMetaDataEvent_id36">some text</span>
> This becomes a problem when you are trying to use outputText to render part
> of a URL or to become a JavaScript string as the output includes the span
> element!
> Looking at the renderer code for outputText it appears the span gets
> generated when the id does not start with "_id", so the question is where has
> the "handleMetaDataEvent" prefix for the id come from?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
