martin,
would be awesome if you could through up a github project of wicket + ajax +
history as an example of how to get all this to work.
rob
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Determine-the-latest-page-in-multi-tabbed-browsing-tp3947526p3991713.html
there are two reasons:
1) our wicket 1.5 application makes heavy use of AJAX e.g. switching
panels. As far as I know the wicket back button support has problems with
AJAX - the DOM modifications are not reflected correctly (see
https://issues.apache.org/jira/browse/WICKET-271)
2) our application
Hi,
In my application we also had similar needs and here is how we solved it.
When an Ajax event is handled we also update the URL's hash with all
necessary information to redo the same event
(target.appendJavaScript('updateHash(someValue)')).
When back button is clicked
Hi,
I'm facing a problem with multi tabbed browsing.
In a wicket application I currently detect browser navigation (back
button) by means of timestamps. As a result I display a warning to the
user telling him that he should not use the back button and subsequently
forward him to the next
since wicket provides backbutton support why are you fighting it?
-igor
On Fri, Oct 28, 2011 at 2:22 AM, Dirk Arnoldt dirk.arn...@1und1.de wrote:
Hi,
I'm facing a problem with multi tabbed browsing.
In a wicket application I currently detect browser navigation (back button)
by means of
