Wrox Programmer Forums
Go Back   Wrox Programmer Forums > Web Programming > JavaScript > Javascript
Javascript General Javascript discussions.
Welcome to the p2p.wrox.com Forums.

You are currently viewing the Javascript section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
Old April 10th, 2004, 04:12 PM
Authorized User
Join Date: Jun 2003
Posts: 53
Thanks: 0
Thanked 0 Times in 0 Posts

Hi Snib:

I understand.

Thanks for your responses. You've been a big help.

Bottom line is that content-changing DHTML involves a lot more work than I thought it did. Not only does one need to make the changes, but one also has to keep track of them as they are made so you can return to the last state if a refresh or back button are used.

Like most really cool things, best used sparingly.

Again, thanks. Much appreciated.

Old April 10th, 2004, 04:23 PM
Friend of Wrox
Join Date: Nov 2003
Posts: 1,285
Thanks: 0
Thanked 2 Times in 2 Posts

No problem.



P2P Member
Old April 12th, 2004, 12:01 AM
Friend of Wrox
Join Date: Jun 2003
Posts: 996
Thanks: 2
Thanked 11 Times in 11 Posts
Send a message via Yahoo to melvik

I still think that page Expiring is better that disabling any button of browser. Why we should close the way for user while u can use of programming.

Hovik Melkomian.
Old April 12th, 2004, 03:00 AM
Authorized User
Join Date: Jun 2003
Posts: 53
Thanks: 0
Thanked 0 Times in 0 Posts

Hello Hovik:

I am in total agreement with you about the Back button, as I believe Snib is. Any other route is a better choice.

In fact, the route I took involves neither cookies nor page expires.

I found that since the controls maintained the correct state (values) after a Refresh or Back button, I could reapply any DHTML generated content changes by writing a routine for the 'onload' event. The routine simply looked at the controls that cause DHTML generated content change, determined their current value, and applied the changes as appropriate.

One more point: I mentioned that the controls maintained their state (values) after a Refresh or Back button. That is true for Mozilla 0.7 and Netscape 7.1. Refresh, in Explorer 6.0, acted just like Reset, the form was cleared of all values. Not just in the form I created, but in other forms I checked it against.


Similar Threads
Thread Thread Starter Forum Replies Last Post
Preventing page refresh from asp.net button hericles ASP.NET 1.0 and 1.1 Professional 2 October 8th, 2008 04:29 PM
don't want the page refresh on button click swati_joshi ASP.NET 1.0 and 1.1 Basics 4 July 31st, 2006 04:37 AM
Refresh Page when User Clicks on Back Button testsubject Visual Studio 2005 1 June 26th, 2006 03:46 AM
refresh the page when using back button hastikeyvan Classic ASP Professional 1 May 12th, 2006 11:08 AM
history.back or hitting the back button won't work lian_a Classic ASP Basics 4 July 29th, 2004 12:14 AM

Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.