It seems you've AJAX'ified the forums within the last few months which is leading to this extremely annoying behaviour: When I'm searching for an answer to an issue I often have to look at posts on page 12 of 24 (for example). Clicking the Back button after reading the post always loads up page 1. Is there a way to get the Back button to behave as it should?
11 Answers, 1 is accepted
0
Hi Neil,
I'm sorry for the inconvenience.
The issue stems from the fact that by default, any ajax call (including Atlas) will not be remembered by the browser as it is done behind the curtains
The browser thus "remembers" only the last postback that has occured on the page.
Our devs are currently thinking of ways to implement this for r.a.d.ajax and we apologize once again for any inconvenience this has caused you.
Thank you for your patience and understanding.
Greetings,
Ubong
the telerik team
0
Loki
Top achievements
Rank 1
Rank 1
answered on 14 Jun 2006, 08:08 AM
Does this mean that we are stuck to the navigation you provide? If I search the forums I want to easily navigate back and forth, but this seems to be impossible - the only option is to click the tiny numbers on the grid pager... Guess how easy is this on my laptop when I don't use the mouse ;-)
0
Hello Luke,
To everybody's regret, this one of the major shortcomings of using callbacks - the browser is not aware of the asynchronous trip made to the server when an ajax call is executed. For this reason there is no "older" page version to go back to. The only workaround is to handle the not-functioning browser back button with a custom back button on the page, and we are in the process of implementing this functionality. Hopefully, it will be live in the next couple of weeks.
Until then, the only way to get around is to use the paging.
Kind regards,
Rob
the telerik team
To everybody's regret, this one of the major shortcomings of using callbacks - the browser is not aware of the asynchronous trip made to the server when an ajax call is executed. For this reason there is no "older" page version to go back to. The only workaround is to handle the not-functioning browser back button with a custom back button on the page, and we are in the process of implementing this functionality. Hopefully, it will be live in the next couple of weeks.
Until then, the only way to get around is to use the paging.
Kind regards,
Rob
the telerik team
0
Michael Ward
Top achievements
Rank 1
Rank 1
answered on 22 Jun 2006, 10:13 AM
I fail to understand why you would put in place such a broken implementation of a technology such as this.
What benefits does the use of AJAX bring in this situation? A small improvement in loading time - the tradeoff being that the back button is annoyingly broken.
Remember new technology shouldn't be used for new technologies sake - looking 'tech savvy' and saving a second or 2 in page refreshing is not worth breaking the browser back button.
What benefits does the use of AJAX bring in this situation? A small improvement in loading time - the tradeoff being that the back button is annoyingly broken.
Remember new technology shouldn't be used for new technologies sake - looking 'tech savvy' and saving a second or 2 in page refreshing is not worth breaking the browser back button.
0
Hi Michael,
I will agree with you, however the usage of callbacks depends on one's requirements. We do provide the tool, however it cannot work with the browser's back button, not because the callback breaks it, but because the browser does not offer the API for us to catch the button press. We understand the importance of this major shortcoming, but unfortunately it is simply beyond our control.
The same holds true for Flash sites, Microsoft's ATLAS, and all other AJAX frameworks offered on the market (try https://www.beatport.com/default.php - it uses custom back button in a flash site). There are many discussions on the topic in the internet which offer ways to handle a custom BACK button on the page. We will try to provide such back/forward functionality with the next version of our controls and on our site.
All the best,
Rob
the telerik team
I will agree with you, however the usage of callbacks depends on one's requirements. We do provide the tool, however it cannot work with the browser's back button, not because the callback breaks it, but because the browser does not offer the API for us to catch the button press. We understand the importance of this major shortcoming, but unfortunately it is simply beyond our control.
The same holds true for Flash sites, Microsoft's ATLAS, and all other AJAX frameworks offered on the market (try https://www.beatport.com/default.php - it uses custom back button in a flash site). There are many discussions on the topic in the internet which offer ways to handle a custom BACK button on the page. We will try to provide such back/forward functionality with the next version of our controls and on our site.
All the best,
Rob
the telerik team
0
Neil N
Top achievements
Rank 1
Iron
Veteran
Iron
Rank 1
Iron
Veteran
Iron
answered on 22 Jun 2006, 01:25 PM
We understand the limitations of AJAX and we make our implementation decisions accordingly. What Michael is saying (and I agree with him) is that implementing AJAX in the forums seems to be putting flash over function. If AJAX slows down the user instead of enhancing his/her experience, why implement it?
If you put up a poll asking members what they prefer - a working back button or AJAXed forums - I'm betting the back button wins out easily. We're here to get info from the forums as quickly as possible.
If you put up a poll asking members what they prefer - a working back button or AJAXed forums - I'm betting the back button wins out easily. We're here to get info from the forums as quickly as possible.
0
Hi Neil,
Thanks for bringing up this issue. After discussing your concerns with our website team, we decided to remove the AJAX from the forums until we are ready with the back functionality mentioned in the previous posts. The changes will take effect on Monday next week.
Sincerely yours,
Natalie Farah
the telerik team
Thanks for bringing up this issue. After discussing your concerns with our website team, we decided to remove the AJAX from the forums until we are ready with the back functionality mentioned in the previous posts. The changes will take effect on Monday next week.
Sincerely yours,
Natalie Farah
the telerik team
0
Michael Ward
Top achievements
Rank 1
Rank 1
answered on 23 Jun 2006, 07:55 AM
I think you've made the correct decision - AJAX is good and has a lot of potential, but in this case it has damaged usability without actually bringing much in the way of functionality.
Thankyou for listening to our feedback.
Thankyou for listening to our feedback.
0
Neil N
Top achievements
Rank 1
Iron
Veteran
Iron
Rank 1
Iron
Veteran
Iron
answered on 01 Jul 2006, 02:10 PM
Thanks very much for making this change. It makes browsing the forums so much easier.
0
Mark Chipman
Top achievements
Rank 1
Rank 1
answered on 02 Jul 2006, 07:52 AM
Natalie (and everyone else):
I hope that these links might be of interest to you in addressing the "back button" issues:
I hope that these links might be of interest to you in addressing the "back button" issues:
- http://codinginparadise.org/weblog/2005/08/ajax-tutorial-tale-of-two-iframes-or.html
- http://codinginparadise.org/weblog/2006/06/ajax-history-support-in-safari.html
-Mark Chipman
0
Hello Mark,
Thanks for providing these links - your help is of great value for us. We are going to check them out when we get to the implementation of the "back" button.
Regards,
Natalie Farah
the telerik team
Thanks for providing these links - your help is of great value for us. We are going to check them out when we get to the implementation of the "back" button.
Regards,
Natalie Farah
the telerik team