You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Sam Hough (JIRA)" <ji...@apache.org> on 2007/09/21 10:08:50 UTC

[jira] Created: (WICKET-994) Ajax requests may happen before DOM is ready

Ajax requests may happen before DOM is ready
--------------------------------------------

                 Key: WICKET-994
                 URL: https://issues.apache.org/jira/browse/WICKET-994
             Project: Wicket
          Issue Type: Bug
          Components: wicket
    Affects Versions: 1.3.0-beta3
         Environment: FF 2, IE 6
            Reporter: Sam Hough


If an Ajax request submits a form that was "recently" updated via Wicket Ajax (using innerHTML) the DOM may not yet be complete so the request is invalid.

Please find attached a Wicket application (unzip into src directory and point web.xml at TestWicketApplication). The quickest way to demonstrate the problem is to get focus on the submit button and hold down the return key. This code updates the whole form, in order to keep the test small, in our production code only a few fields are updated but the problem is the same.

Please let me know if I should change the test to be more useful.

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

[jira] Resolved: (WICKET-994) Ajax requests may happen before DOM is ready

Posted by "Matej Knopp (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/WICKET-994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matej Knopp resolved WICKET-994.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 1.3.0-beta4

Already fixed.

> Ajax requests may happen before DOM is ready
> --------------------------------------------
>
>                 Key: WICKET-994
>                 URL: https://issues.apache.org/jira/browse/WICKET-994
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.3.0-beta3
>         Environment: FF 2, IE 6
>            Reporter: Sam Hough
>            Assignee: Matej Knopp
>             Fix For: 1.3.0-beta4
>
>         Attachments: test.zip
>
>
> If an Ajax request submits a form that was "recently" updated via Wicket Ajax (using innerHTML) the DOM may not yet be complete so the request is invalid.
> Please find attached a Wicket application (unzip into src directory and point web.xml at TestWicketApplication). The quickest way to demonstrate the problem is to get focus on the submit button and hold down the return key. This code updates the whole form, in order to keep the test small, in our production code only a few fields are updated but the problem is the same.
> Please let me know if I should change the test to be more useful.

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

[jira] Assigned: (WICKET-994) Ajax requests may happen before DOM is ready

Posted by "Matej Knopp (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/WICKET-994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matej Knopp reassigned WICKET-994:
----------------------------------

    Assignee: Matej Knopp

> Ajax requests may happen before DOM is ready
> --------------------------------------------
>
>                 Key: WICKET-994
>                 URL: https://issues.apache.org/jira/browse/WICKET-994
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.3.0-beta3
>         Environment: FF 2, IE 6
>            Reporter: Sam Hough
>            Assignee: Matej Knopp
>         Attachments: test.zip
>
>
> If an Ajax request submits a form that was "recently" updated via Wicket Ajax (using innerHTML) the DOM may not yet be complete so the request is invalid.
> Please find attached a Wicket application (unzip into src directory and point web.xml at TestWicketApplication). The quickest way to demonstrate the problem is to get focus on the submit button and hold down the return key. This code updates the whole form, in order to keep the test small, in our production code only a few fields are updated but the problem is the same.
> Please let me know if I should change the test to be more useful.

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

[jira] Updated: (WICKET-994) Ajax requests may happen before DOM is ready

Posted by "Sam Hough (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/WICKET-994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sam Hough updated WICKET-994:
-----------------------------

    Attachment: test.zip

Description of how to use the file in initial posting.

> Ajax requests may happen before DOM is ready
> --------------------------------------------
>
>                 Key: WICKET-994
>                 URL: https://issues.apache.org/jira/browse/WICKET-994
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.3.0-beta3
>         Environment: FF 2, IE 6
>            Reporter: Sam Hough
>         Attachments: test.zip
>
>
> If an Ajax request submits a form that was "recently" updated via Wicket Ajax (using innerHTML) the DOM may not yet be complete so the request is invalid.
> Please find attached a Wicket application (unzip into src directory and point web.xml at TestWicketApplication). The quickest way to demonstrate the problem is to get focus on the submit button and hold down the return key. This code updates the whole form, in order to keep the test small, in our production code only a few fields are updated but the problem is the same.
> Please let me know if I should change the test to be more useful.

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