T
Todd A
Here is a simple example of the problem I am experiencing:
Page1.aspx
--has a simple html hyperlink that points to Page2.aspx
Page2.aspx
--has a simple html hyperlink that points to Page3.aspx and uses the
target="_blank" attribute, so Page3.aspx opens in a new window
Page3.aspx
--has just some static html information
Here is the problem
User starts on Page1, proceeds to Page2, and then to Page3 in a new window
User closes the browser window that has Page3
User now sees the browser window with Page2 in it.
User clicks the BACK button to get to Page1
Page1.Page_Load is executing, (but should not be)
All is fine except Page1.Page_Load firing. Why would the Page1.Page_Load
event fire by using the back button? Isn't Page1 supposed to be delivered
from the cache instead of initiating a server request?
If you take away the target="_blank" from the hyperlink on Page2, then
Page1.Page_Load does not fire in the above example. It seems opening a
webform in a new window is causing the problem.
Has anyone else experienced this, and if so, is there a methodolgy or fix
for preventing Page1.Page_Load?
Thanks,
Page1.aspx
--has a simple html hyperlink that points to Page2.aspx
Page2.aspx
--has a simple html hyperlink that points to Page3.aspx and uses the
target="_blank" attribute, so Page3.aspx opens in a new window
Page3.aspx
--has just some static html information
Here is the problem
User starts on Page1, proceeds to Page2, and then to Page3 in a new window
User closes the browser window that has Page3
User now sees the browser window with Page2 in it.
User clicks the BACK button to get to Page1
Page1.Page_Load is executing, (but should not be)
All is fine except Page1.Page_Load firing. Why would the Page1.Page_Load
event fire by using the back button? Isn't Page1 supposed to be delivered
from the cache instead of initiating a server request?
If you take away the target="_blank" from the hyperlink on Page2, then
Page1.Page_Load does not fire in the above example. It seems opening a
webform in a new window is causing the problem.
Has anyone else experienced this, and if so, is there a methodolgy or fix
for preventing Page1.Page_Load?
Thanks,