[jira] Resolved: (WICKET-3352) Google Chrome 8 browser history and multipart form ajax submit

["Igor Vaynberg (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/WICKET-3352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Igor Vaynberg resolved WICKET-3352.
-----------------------------------

    Resolution: Won't Fix
      Assignee: Igor Vaynberg

this is not really a bug. we make no guarantees about ajax and history. further, there is no other way, yet, to do a multipart upload properly without an iframe, so we are stuck with this.

> Google Chrome 8 browser history and multipart form ajax submit
> --------------------------------------------------------------
>
>                 Key: WICKET-3352
>                 URL: https://issues.apache.org/jira/browse/WICKET-3352
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.5-M3
>         Environment: Ghrome 8, wicket 1.5-SNAPSHOT
>            Reporter: Ivan Vasilev
>            Assignee: Igor Vaynberg
>         Attachments: quickstart.rar
>
>
> The problem can be reproduced with Chrome and it doesn't exist in Firefox.
> With the attached quickstart:
> 1. In Chrome open localhost:8080, the Homepage (TestPage) is displayed
> 2. Follow the link and go to TestPageBrowserHistory page. In it there is a multipart form which is submitted via AjaxButton.
> 3. Submit the form several times.
> 4. Click the back button of the browser. In theory the browser should redirect to the Homepage, which was first opened, since the form has been submitted only via ajax. However the browser redirects to TestPageBrowserHistory instead of homepage.
> If the form has been submitted, for example, 3 times then the browser's back button needs to be clicked 4 times in order to go back to the homepage. Each form submit is added to the browser history. 
> If the form is not multipart everything works fine.
> I checked wicket-ajax.js file and found the following:
> The multipart form is submitted by handleMultipart function. This function creates an iframe element and adds it to the dom tree. The form's target is set to the iframe. I think that by creating the iframe and adding it to dom tree, this is actually added to the browser's history and the described effect can be observed. Thanks.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.