[
https://issues.apache.org/jira/browse/MYFACES-3400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13156748#comment-13156748
]
Werner Punz commented on MYFACES-3400:
--------------------------------------
Ok I did a deeper investigation. on the issue, and I cannot recommend to
support more than UTF-8 in the ajax requests for now. The issue simply is
browser limitations on literally 60% of all browsers and limitations in the
encoding on the javascript side.
As far as it seems the implementations handle the non utf pages and mixed utf
ajax requests quite fine. So I will resolve this issue as invalid.
> jsf.js: improvement of the encoding handling
> --------------------------------------------
>
> Key: MYFACES-3400
> URL: https://issues.apache.org/jira/browse/MYFACES-3400
> Project: MyFaces Core
> Issue Type: New Feature
> Affects Versions: 2.0.10, 2.1.4
> Reporter: Werner Punz
> Assignee: Werner Punz
>
> Currently the default behavior for the encoding is UTF-8 for an ajax request
> with a config param for overriding the default encoding. Now due to a user
> request this does not work out. We need to have the ajax encoding more
> flexible. The idea is to detect the ajax encoding one way or the other
> (probably by dom parsing) and to adjust the request encoding accordingly.
> Investigation and code will be logged under this issue. However it is not
> sure if the final result will make it into 2.1, accordingly to the JSF-EG and
> the Mojarra people we will discuss it out whether the fixup will make it into
> the 2.1 codebase or not.
--
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
