By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
425,542 Members | 1,740 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 425,542 IT Pros & Developers. It's quick & easy.

ext 3.5 History back button from different page

P: n/a
Max
I recently moved to ASPnet Ext 3.5
What I can't get with Ajax and History browser managemet is this:

User fills some fields (dropdown and textbox) on page 1 (all are in an
update panel)
User clicks Submit Button
I write the data into a DB
I add a history point with ScriptManager to be able to get back to this
point with browser back button
Page 2 is loaded with a response.redirect() command
At this point , clicking the back browser button, I get page1 completely
blank. I moved the submit button in and out of the update panel, same
result.
It seems that the page is not cached correctly, or the history point is not
added.

But, If I click submit button to validate/write into the DB etc.. and then
ANOTHER button just to go to page2, then it works (wow! what a high
technology)

Does the history management work ONLY as long as we stay in the SAME page?
Is really like this? Where is the power of Ajax if a simple, traditional
way of ASP programming doesn't have such a huge limitation?

Thanks Max


Jun 27 '08 #1
Share this Question
Share on Google+
2 Replies


P: n/a
you are missing the point of the ajax history object. ajax postbacks do not
go into the browser history, so some client coding is required usually with
bookmarks.

there are several ajax history solutions and the extensions use a fairly
typical model. when your code save a history point, you pass a savestate.
when the browser navigates thru a ajax history, the ajax control fire's an
event, and your client code should look at the state make the page match.

the ajax browser history is only used for ajax postbacks, once an actual
post is done, then you are back to standard browser history.

if you want history support, you need to learn how it works, and code your
site to support it.

-- bruce (sqlwork.com)
"Max" wrote:
I recently moved to ASPnet Ext 3.5
What I can't get with Ajax and History browser managemet is this:

User fills some fields (dropdown and textbox) on page 1 (all are in an
update panel)
User clicks Submit Button
I write the data into a DB
I add a history point with ScriptManager to be able to get back to this
point with browser back button
Page 2 is loaded with a response.redirect() command
At this point , clicking the back browser button, I get page1 completely
blank. I moved the submit button in and out of the update panel, same
result.
It seems that the page is not cached correctly, or the history point is not
added.

But, If I click submit button to validate/write into the DB etc.. and then
ANOTHER button just to go to page2, then it works (wow! what a high
technology)

Does the history management work ONLY as long as we stay in the SAME page?
Is really like this? Where is the power of Ajax if a simple, traditional
way of ASP programming doesn't have such a huge limitation?

Thanks Max


Jun 27 '08 #2

P: n/a
Max

Maybe I cannot explain in the best way, bu I'm not missing the point. I
understand how the History points works with Ajax 3.5
The state-of-the-art limitation is that the history point concept doesn't
apply if you add one when moving from a webform to another. Try, it takes 3
minutes:
type something in a textbox into an updatepanel, and press a button that
fixes an history point and calls another webform.
Get back and the textbox of first webform is empty. Totally different from
non-Ajax pages.
I've found other long topics after further search, watched MS videos, and
the conclusion is unfortunately the same.
Max
"bruce barker" <br*********@discussions.microsoft.comha scritto nel
messaggio news:E5**********************************@microsof t.com...
you are missing the point of the ajax history object. ajax postbacks do
not
go into the browser history, so some client coding is required usually
with
bookmarks.

there are several ajax history solutions and the extensions use a fairly
typical model. when your code save a history point, you pass a savestate.
when the browser navigates thru a ajax history, the ajax control fire's an
event, and your client code should look at the state make the page match.

the ajax browser history is only used for ajax postbacks, once an actual
post is done, then you are back to standard browser history.

if you want history support, you need to learn how it works, and code your
site to support it.

-- bruce (sqlwork.com)
"Max" wrote:
>I recently moved to ASPnet Ext 3.5
What I can't get with Ajax and History browser managemet is this:

User fills some fields (dropdown and textbox) on page 1 (all are in an
update panel)
User clicks Submit Button
I write the data into a DB
I add a history point with ScriptManager to be able to get back to this
point with browser back button
Page 2 is loaded with a response.redirect() command
At this point , clicking the back browser button, I get page1 completely
blank. I moved the submit button in and out of the update panel, same
result.
It seems that the page is not cached correctly, or the history point is
not
added.

But, If I click submit button to validate/write into the DB etc.. and
then
ANOTHER button just to go to page2, then it works (wow! what a high
technology)

Does the history management work ONLY as long as we stay in the SAME
page?
Is really like this? Where is the power of Ajax if a simple, traditional
way of ASP programming doesn't have such a huge limitation?

Thanks Max



Jun 27 '08 #3

This discussion thread is closed

Replies have been disabled for this discussion.