[
https://issues.apache.org/jira/browse/MYFACES-3412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13159576#comment-13159576
]
Werner Punz edited comment on MYFACES-3412 at 11/29/11 10:23 PM:
-----------------------------------------------------------------
I still think the problem is somewhat with us, do we have the right simply to
tamper with the markup passed down by the lib? if a <!-- ---> is passed down,
we should not make a <![CDATA[ out of it no matter what.
Especially if <!-- --> is a perfectly fine xhtml construct and in the end is
embedded into an outer CDATA section anyway where everything can be placed in
unescaped except for ]]>
We should not be wiser than the user or library which generates the markup.
Regarding the partial response encoding. The content always is xml which is
returned, no matter what the header says, the spec leaves there no option. The
actual markup content is in itself in a cdata block.<!-- --> is absolutely
valid in CDATA.
Could it be that the CDATA stuff was added as quick fix for facelets modes
where comments were removed?
was (Author: werpu):
I still think the problem is somewhat with us, do we have the right simply
to tamper with the markup passed down by the lib? if a <!-- ---> is passed
down, we should not make a <![CDATA[ out of it no matter what.
Especially if <!-- --> is a perfectly fine xhtml construct and in the end is
embedded into an outer CDATA section anyway where everything can be placed in
unescaped except for ]]>
We should not be wiser than the user or library which generates the markup.
Regarding the partial response encoding. The content always is xml which is
returned, no matter what the header says, the spec leaves there no option. The
actual markup content is in itself in a cdata block.<!-- --> is absolutely
valid in CDATA.
> updated AJAX values sometimes delete other elements
> ---------------------------------------------------
>
> Key: MYFACES-3412
> URL: https://issues.apache.org/jira/browse/MYFACES-3412
> Project: MyFaces Core
> Issue Type: Bug
> Affects Versions: 2.0.10, 2.1.4
> Reporter: Mark Struberg
> Assignee: Werner Punz
> Attachments: ajaxbug.zip
>
>
> The attached examples shows a problem I face after updating to the latest
> 2.0.10/11 and 2.1.4/5 MyFaces versions.
> I have 2 primefaces date pickers inside a h:panelGroup. Both date pickers
> create ajax requests and refresh their values. If you click one of them (both
> update the whole panelGroup), the 2nd date picker disapears.
> This might have something to do with the AJAX js rework?
> I can easily work around this issue, but I'm not sure which other problems
> might arise as well, thus we better fix this
--
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
