[jira] [Comment Edited] (WICKET-5216) FileUpload: IE9 is not redirecting to response body while uploading file using wicket modal page(embedded within a JSP)

["Frédéric Donckels (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/WICKET-5216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13753440#comment-13753440 ] 

Frédéric Donckels edited comment on WICKET-5216 at 8/29/13 8:53 AM:
--------------------------------------------------------------------

This happens to me too.
IE 9, and because of some customer constraints, we had to add a "X-UA-Compatible:IE=8" value in the headers, this switches IE to "DocumentMode:IE8 standards".
Wicket: 1.5.10
Win 7, 64 bit

see attached screenshot (debugger_output.jpg) to view the spurious dash. Please reopen the ticket
(in the meantime, I'll monkeypatch the Wicket._htmlToDomDocument for this specific page, but this is not a long-term solution)
                
      was (Author: fdonckels):
    This happens to me too.
IE 9, and because of some customer constraints, we had to add a "X-UA-Compatible:IE=8" value in the headers, this switches IE to "DocumentMode:IE8 standards".
Wicket: 1.5.10
Win 7, 64 bit

see attached screenshot to view the spurious dash. Please reopen the ticket
(in the meantime, I'll monkeypatch the Wicket._htmlToDomDocument for this specific page, but this is not a long-term solution)
                  
> FileUpload: IE9 is not redirecting to response body while uploading file using wicket modal page(embedded within a JSP)
> -----------------------------------------------------------------------------------------------------------------------
>
>                 Key: WICKET-5216
>                 URL: https://issues.apache.org/jira/browse/WICKET-5216
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.5.5
>            Reporter: Chandan Sethi
>         Attachments: debugger output.jpg
>
>
> In case of IE9 while processing multipart AJAX request we get XMLDocument as NULL. So wicket uses its helper JS functions Wicket._htmlToDomDocument() and Wicket._createXmlDocument() functions to load XML document. The text used by these two methods is of the following form
> "- <ajax-response>\r\n- <redirect>\r\n- <![CDATA[ /wicket/page?17\r\n ]]> \r\n </redirect>\r\n </ajax-response>"
> The function Wicket._htmlToDomDocument() trims the above text and replaces all occurrence of ‘/r/n-’. The resultant text (i.e. ‘‘- <ajax-response> <redirect> <![CDATA[ /wicket/page?13 ]]> </redirect> </ajax-response>’) is then passed to function Wicket._createXmlDocument() for creating XML Document. However function Wicket._createXmlDocument() is throwing error as it is unable to load XML document from the provided text. Function Wicket._createXmlDocument() gets failed to load XML document from text because text has an error i.e. it contains extra ‘-’ at the start of the text. Due to the error wicket does not found <ajax-response> element in the response. Hence IE9 is not able to process the response.
> If we remove extra ‘-’ from the text then wicket loads XML document successfully and IE9 gets redirect to response successfully.
> Please note that here default document mode for IE9 is Quirks.
> Note: In case of IE8 we get appropriate XMLDocument therefore wicket does not call helper JS functions to get the XML Document. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira