>
> Can't you fix that with a
> getPage().dirty();
> in the Ajax request handler?
Hmm tried your suggestion, but no luck. How would it help anyway? It's
dirty() that is causing the page to change version in the first place
right? RefreshingView.onPopulate() -> MarkupContainer.removeAll() ->
Compo
> Thus the browser still shows the old version in the URL. But all future Ajax
> requests are targetting a different page version than visible in the browser
> URL :(.
Can't you fix that with a
getPage().dirty();
in the Ajax request handler?
- Tor Iver
--
Hi,
in Ajax requests the page id is not incremented, to keep the page
version in the browser's url in sync with the state on the server.
When the page is refreshed (F5), the following happens:
- WebPageRenderer#respond() checks whether the url has changed, which it
has not yet. So no redirect
I'm getting some inconsistent behavior with
AjaxFallbackDefaultDataTable. Here are two scenarios that can be run on
wicket-examples:
*Scenario 1*
1 - navigate to
http://wicketstuff.org/wicket/repeater/wicket/bookmarkable/org.apache.wicket.examples.repeater.AjaxDataTablePage
2 - click the link to n
