You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Martín Bigio (Created JIRA)" <ji...@apache.org> on 2011/12/12 22:29:30 UTC

[jira] [Created] (WICKET-4291) Problem in Chrome when adding panel with modal windows to ajax request target

Problem in Chrome when adding panel with modal windows to ajax request target
-----------------------------------------------------------------------------

                 Key: WICKET-4291
                 URL: https://issues.apache.org/jira/browse/WICKET-4291
             Project: Wicket
          Issue Type: Bug
          Components: wicket, wicket-extensions
    Affects Versions: 1.5.3
         Environment: Chromium 8.0 & Ubuntu 10/10
            Reporter: Martín Bigio


When trying to replace an empty panel with one that contains a modal window during an AJAX request the DOM insn't modified. The wicket ajax debug windows shows that the request is being made and the answert, but when trying to apply the changes to the DOM the debug windows hangs after this message: "INFO: Response parsed. Now invoking steps...". If I press F5 to refresh, the chages are shown indicating that the request was processed correctly and the changes in the page hierarchy were persisted. However if I click again in the link that fires the ajax request the wicket debug windows shows this message: "INFO: Channel busy - postponing...".

We couldn't reproduce this issue in firefox. I'll attach a quickstart for reproducing the problem. When running it locally if I click in the link the DOM isn't updated as suppossed to.

--
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

       

[jira] [Updated] (WICKET-4291) Problem in Chrome when adding panel with modal windows to ajax request target

Posted by "Martín Bigio (Updated JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/WICKET-4291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martín Bigio updated WICKET-4291:
---------------------------------

    Attachment: sga-ajaxqs.zip
    
> Problem in Chrome when adding panel with modal windows to ajax request target
> -----------------------------------------------------------------------------
>
>                 Key: WICKET-4291
>                 URL: https://issues.apache.org/jira/browse/WICKET-4291
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket, wicket-extensions
>    Affects Versions: 1.5.3
>         Environment: Chromium 8.0 & Ubuntu 10/10
>            Reporter: Martín Bigio
>         Attachments: sga-ajaxqs.zip
>
>
> When trying to replace an empty panel with one that contains a modal window during an AJAX request the DOM insn't modified. The wicket ajax debug windows shows that the request is being made and the answert, but when trying to apply the changes to the DOM the debug windows hangs after this message: "INFO: Response parsed. Now invoking steps...". If I press F5 to refresh, the chages are shown indicating that the request was processed correctly and the changes in the page hierarchy were persisted. However if I click again in the link that fires the ajax request the wicket debug windows shows this message: "INFO: Channel busy - postponing...".
> We couldn't reproduce this issue in firefox. I'll attach a quickstart for reproducing the problem. When running it locally if I click in the link the DOM isn't updated as suppossed to.

--
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

       

[jira] [Resolved] (WICKET-4291) Problem in Chrome when adding panel with modal windows to ajax request target

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

Martin Grigorov resolved WICKET-4291.
-------------------------------------

    Resolution: Cannot Reproduce

Your app behaves the same way in Chrome 17.x and Firefox 8.
The EmptyPanel is replaced with SimplePanel without any problems. Since there is no code that calls modalWindow.show(target) the modal itself is never shown.

I needed to recreate the quickstart because your attachment was broken somehow...
                
> Problem in Chrome when adding panel with modal windows to ajax request target
> -----------------------------------------------------------------------------
>
>                 Key: WICKET-4291
>                 URL: https://issues.apache.org/jira/browse/WICKET-4291
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket, wicket-extensions
>    Affects Versions: 1.5.3
>         Environment: Chromium 8.0 & Ubuntu 10/10
>            Reporter: Martín Bigio
>         Attachments: sga-ajaxqs.zip
>
>
> When trying to replace an empty panel with one that contains a modal window during an AJAX request the DOM insn't modified. The wicket ajax debug windows shows that the request is being made and the answert, but when trying to apply the changes to the DOM the debug windows hangs after this message: "INFO: Response parsed. Now invoking steps...". If I press F5 to refresh, the chages are shown indicating that the request was processed correctly and the changes in the page hierarchy were persisted. However if I click again in the link that fires the ajax request the wicket debug windows shows this message: "INFO: Channel busy - postponing...".
> We couldn't reproduce this issue in firefox. I'll attach a quickstart for reproducing the problem. When running it locally if I click in the link the DOM isn't updated as suppossed to.

--
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