[
https://issues.apache.org/jira/browse/TRINIDAD-1756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Robinson resolved TRINIDAD-1756.
---------------------------------------
Resolution: Fixed
Fix Version/s: 2.0.0.3-core
1.2.14-core
Fixed in Safari and Chrome. Tested using Chrome beta on mac and linux and
Safari on mac.
> Trinidad IFrame PPR does not work in google chrome
> --------------------------------------------------
>
> Key: TRINIDAD-1756
> URL: https://issues.apache.org/jira/browse/TRINIDAD-1756
> Project: MyFaces Trinidad
> Issue Type: Bug
> Components: Components
> Affects Versions: 1.2.13-core
> Environment: Google Chrome 5.0.307.11 (Official Build 39572) beta
> WebKit 532.9
> V8 2.0.6.6
> User Agent Mozilla/5.0 (X11; U; Linux x86_64; en-US) AppleWebKit/532.9
> (KHTML, like Gecko) Chrome/5.0.307.11 Safari/532.9
> Reporter: Andrew Robinson
> Assignee: Andrew Robinson
> Priority: Critical
> Fix For: 1.2.14-core , 2.0.0.3-core
>
>
> iframe based PPR, used for input file post backs does not work in google
> chrome. The resulting DOM document is just an empty HTML document:
> <html><head></head><body></body></html>
> The PPR contents are completely lost when the browser parses the request.
> Either the payload needs to be changed or some kind of XML header needs to be
> sent down to stop Chrome from obliterating the content. My guess is that it
> sees a non-HTML page and ignores the response as invalid content.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
