You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Stefan Renz <s....@efonds.com> on 2013/06/11 16:46:18 UTC
Problem with WiQuery Tab component after page reload
Hi,
I've observed the following behavior with WiQuery's Tabs-component:
after reloading a page with a tabs component on it (or by navigating the
browser history), one can't switch the active tab anymore -- the
component always jumps back. The browser makes a new request.
Apparently, Wicket loads a specific page version from the page store,
which is stuck on the tab. Removing the version number from the URL
works as expected.
Did anyone also observe this behavior, or has anyone a suggestion to
workaround or fix that?
The least thing I could do is to come up with a quickstart for this,
which is attached.
We're talking about Wicket 6.6.0 and WiQuery 6.6.0 here, I've also tried
with 6.5.0.
Thanks, bye
Stefan
Re: Problem with WiQuery Tab component after page reload
Posted by Stefan Renz <s....@efonds.com>.
I forgot to mention that this happens with an ITabsAjaxEvent handler
installed on the Tabs component... so is this a stateful/stateless thing?
Bye
Stefan
Stefan Renz wrote:
> Hi,
>
> I've observed the following behavior with WiQuery's Tabs-component:
> after reloading a page with a tabs component on it (or by navigating the
> browser history), one can't switch the active tab anymore -- the
> component always jumps back. The browser makes a new request.
> Apparently, Wicket loads a specific page version from the page store,
> which is stuck on the tab. Removing the version number from the URL
> works as expected.
>
> Did anyone also observe this behavior, or has anyone a suggestion to
> workaround or fix that?
>
> The least thing I could do is to come up with a quickstart for this,
> which is attached.
>
> We're talking about Wicket 6.6.0 and WiQuery 6.6.0 here, I've also tried
> with 6.5.0.
>
> Thanks, bye
> Stefan
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
-- im Auftrag der eFonds Solutions AG, +49-89-579494-3417
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Problem with WiQuery Tab component after page reload
Posted by Stefan Renz <s....@efonds.com>.
Hi,
has no-one observed this yet? Shall I file an issue?
Bye
Stefan
Stefan Renz wrote:
> Hi,
>
> I've observed the following behavior with WiQuery's Tabs-component:
> after reloading a page with a tabs component on it (or by navigating the
> browser history), one can't switch the active tab anymore -- the
> component always jumps back. The browser makes a new request.
> Apparently, Wicket loads a specific page version from the page store,
> which is stuck on the tab. Removing the version number from the URL
> works as expected.
>
> Did anyone also observe this behavior, or has anyone a suggestion to
> workaround or fix that?
>
> The least thing I could do is to come up with a quickstart for this,
> which is attached.
>
> We're talking about Wicket 6.6.0 and WiQuery 6.6.0 here, I've also tried
> with 6.5.0.
>
> Thanks, bye
> Stefan
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
--
im Auftrag der eFonds Solutions AG, +49-89-579494-3417
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Problem with WiQuery Tab component after page reload
Posted by Stefan Renz <s....@efonds.com>.
I forgot to mention that this happens with an ITabsAjaxEvent handler
installed on the Tabs component... so is this a stateful/stateless thing?
Bye
Stefan
Stefan Renz wrote:
> Hi,
>
> I've observed the following behavior with WiQuery's Tabs-component:
> after reloading a page with a tabs component on it (or by navigating the
> browser history), one can't switch the active tab anymore -- the
> component always jumps back. The browser makes a new request.
> Apparently, Wicket loads a specific page version from the page store,
> which is stuck on the tab. Removing the version number from the URL
> works as expected.
>
> Did anyone also observe this behavior, or has anyone a suggestion to
> workaround or fix that?
>
> The least thing I could do is to come up with a quickstart for this,
> which is attached.
>
> We're talking about Wicket 6.6.0 and WiQuery 6.6.0 here, I've also tried
> with 6.5.0.
>
> Thanks, bye
> Stefan
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
--
im Auftrag der eFonds Solutions AG, +49-89-579494-3417
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org