After some digging, it's related to the multipart ajax request via
posting an iframe.

The iframe is removed in the onload of the iframe ( see
) and it seems to be problematic for Firefox.

Looks like there is some literature about it here:

and using a pattern like the following should fix it:
iframe.onload = function(){
    // Do work with the content of the iframeā€¦

    }, 0);

Note: we are using Wicket 6.8.0 and Firefox 21.

Should I open a JIRA and should I attach a quickstart to it? I'm AFK
till monday but should be able to do it on monday if needed.



On Fri, Jun 7, 2013 at 4:34 PM, Guillaume Smet <guillaume.s...@gmail.com> wrote:
> Hi,
> For quite a while now, we are seeing a weird behavior with Firefox: as
> soon as Wicket does an Ajax call, the tab title is changed to
> "Connecting..." and it doesn't get back to the original page title at
> all, even after the Ajax call returned.
> Does anybody else see this behavior?
> We don't see it with any other site doing Ajax calls, just with Wicket app.
> It looks like a detail but it's quite annoying to have a bunch of tabs
> named "Connecting...".
> Thanks for your feedback.
> --
> Guillaume

To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Reply via email to