To make the browser's back/forward buttons work is a challenge to each AJAX-driven web application. Remember Gmail had the same problem in their first beta and now they fixed it. It's possible to fake the browser history in order to get correct javascript calls every time the user clicks on those buttons. It's on my todo-list to implement a work around that enables the correct behavior of the browser history.
Just note that we are aware of that problem and it will be fixed. Regards, Thomas Dan Schaper wrote: > One thing I've noticed, if I use the RoundCube navigation icons, then > all of the problems with messages appearing not to move, or not being > deleted, then things go smooth and accurate. Also the hourglass notice > at the top-center of the page always displays. However, if I use the > forwards/backwards navigation of my webbrowser (IE at the moment.), then > the message list display does not always update, nor do I get the > top-center update display. > > Haven't coded HTML or JS in ages, but is there a way to prevent usage of > the browsers navigation shortcuts, and force the use of RC's icons for > navigation? Or perhaps the login screen should have a say something like > "Please use the navigation icons within RoundCube, do not use your > browsers forward or reverse features"? > > Layman's guess, but when using the browsers forward/reverse, then the JS > functions do not always trigger, and the browser is caching the main > display page, and not showing a current view. And yes, Cache is set to > false, but would a pragma no-cache prevent the browser from loading a > stale page? > > -- > Dan Schaper
