[
https://issues.apache.org/jira/browse/MYFACES-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12506512
]
Mario Ivankovits commented on MYFACES-1666:
-------------------------------------------
Its not that it might confuse me, but it allows one to reuse this configuration
for other "non ri compatible" stuff too ... which I think is not good.
I'd like it to have it fine grained.
Just to make it a little bit more complicated to find a conclusion ;-) I think
we can drop the word "STRICT", SUCCESSIVE_SPACE_ENCODING would be sufficient.
> HtmlResponseWriterImpl implements different encoding behaviour for the two
> writeText methods
> --------------------------------------------------------------------------------------------
>
> Key: MYFACES-1666
> URL: https://issues.apache.org/jira/browse/MYFACES-1666
> Project: MyFaces Core
> Issue Type: Bug
> Components: General
> Affects Versions: 1.1.5
> Reporter: Manfred Geiler
> Assignee: Manfred Geiler
>
> HtmlResponseWriterImpl implements different behaviour for the two writeText
> methods:
> * writeText(Object value, String componentPropertyName) does not encode
> successive spaces and newlines
> * writeText(char cbuf[], int off, int len) does encode successive spaces and
> newlines
> RI does not encode in both variants.
> IMO both methods SHOULD encode successive spaces and newlines to render the
> corresponding HTML syntax ( and <br/>).
> Therefore we should (re)add this feature and make it switchable via a MyFaces
> Option "STRICT_RI_MODE" or something like that.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
