when a user clicks back to get to my site, I want it to run a javascript
function.
can you detect when the FORWARD button is greyed out?
Randy Webb said:|-|erc said the following on 8/21/2005 10:10 PM:
No. It is none of your business where I came from or where I am going.
Besides, what difference does it make?
|-|erc said:when a user clicks back to get to my site, I want it to run a javascript
function.
can you detect when the FORWARD button is greyed out?
|-|erc said:windows.history.length will tell me how many sites are in your queue, so
you are wrong.
FORM --- submit ---> PAGE 2 [click Back to edit]
When you click back (from my own page again), the form data is still there
and you can edit it.
But the javascript variables are reset so I need to
reinitialise them using data from the form.
John W. Kennedy said:Seeing that some browsers cache the DOM and others do not, I doubt any
general solution is even possible.
RobG said:The reply was in regard to determining if the forward button is enabled
or not. How does the history length tell you that?
Or are you saying that it *is* your business where Randy came from?
FORM --- submit ---> PAGE 2 [click Back to edit]
When you click back (from my own page again), the form data is still there
and you can edit it.
Are you using your back button or the browsers? If it's yours, then you
can attempt to do what you like by posting data to the server but if
it's the browser back button, then some browsers retain the values and
others don't.
But the javascript variables are reset so I need to
reinitialise them using data from the form.
Then (attempt) to do so onload and expect to fail some of the time.
|-|erc said:I get the default form values when I tried that... not onload but directly
parsed, code not contained in a function body. Onload may make a
difference.... just a pain its in my header file.
RobG said:Try the following:
<body onload="alert(document.formA.elementA.value);">
<form name="formA">
<input type="text" value="fred" name="elementA">
</form>
</body>
In both IE and Firefox the following behaviour is observed:
1. On initial load, get an alert with 'fred'.
2. Change the value to 'sue', click reload or ctrl+R, get 'sue'.
3. Navigate to another site, press browser 'back' button, get 'sue'.
4. Click in address bar, press enter, get 'fred'.
If you run the script after the form but before onload, you will get the
default values, not the 'current' ones. It seems that the browsers are
loading the page, then looking at the cache to replace form values, then
running onload.
|-|erc said:so there's nothing like windows.history.length
but it tells you how far through the history you are?
say I wanted to make my own fast forward and fast back buttons.
go +10 or go -10 pages, but when you're near the ends, it changes to +2
or -2 pages.
That's impossible because you have no idea where in the history stack you
are??
Randy Webb said:|-|erc said the following on 8/21/2005 10:10 PM:
No. It is none of your business where I came from or where I am going.
Besides, what difference does it make?
windows.history.length will tell me how many sites are in your queue, so
you are wrong.
FORM --- submit ---> PAGE 2 [click Back to edit]
When you click back (from my own page again), the form data is still there
and you can edit it. But the javascript variables are reset so I need to
reinitialise them using data from the form.
Randy Webb said:|-|erc said the following on 8/21/2005 10:31 PM:
Randy Webb said:|-|erc said the following on 8/21/2005 10:10 PM:
when a user clicks back to get to my site, I want it to run a javascript
function.
can you detect when the FORWARD button is greyed out?
No. It is none of your business where I came from or where I am going.
Besides, what difference does it make?
windows.history.length will tell me how many sites are in your queue, so
you are wrong.
FORM --- submit ---> PAGE 2 [click Back to edit]
When you click back (from my own page again), the form data is still there
and you can edit it. But the javascript variables are reset so I need to
reinitialise them using data from the form.
That does not tell you:
1) How many sites *before* your site.
2) How many sites *after* your site.
3) What and where I was.
What's in my history trail is none of your business.
It tells you "how many sites are in your history trail" so your deduction is
flawed.
I can put up a page "BEEN TO 250 SITES TODAY ALREADY.... TIRED OF SURFING
YET?"
or "JUST STARTING ON THE COMPUTER TODAY... BEEN TO A HALF DOZEN SITES?"
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.