
Signature
Randy
comp.lang.javascript FAQ - http://jibbering.com/faq & newsgroup weekly
Javascript Best Practices - http://www.JavascriptToolbox.com/bestpractices/
>Ed Jay said the following on 12/30/2005 3:38 PM:
>> I'm using history.go(-n) to return to a page for editing without
[quoted text clipped - 21 lines]
>
>Then that is damn near impossible. You can't edit a page that isn't loaded.
I understand. I'm looking for a way to load a page from the cache and
modify it from within the script. The problem I have is that apparently
the page doesn't get loaded until I exit the script. I am/was looking for
a way around it.
The only thing I can think of is to modify the page when I submit the
form, so if I return to it I'm in the 'edit mode.'
The difference between normal and edit modes is that in the normal mode,
the form is submitted to the next page in order, whereas in the edit mode
the form is submitted to the final page. There are six pages of data entry
and a final report page. I want to return to individual pages in the edit
mode from the final page and return to the final page after editing so I
don't have to re-enter the data on subsequent pages.
I can, of course, mark a page to be in the edit mode when I submit it the
first time, but the guy entering data could conceivably realize he made an
error and use his browser's back button to return to correct the problem,
and then submit the corrected data only to find that he skipped over empty
pages to get to the final page.
Yes, I could provide instructions to not do it, but I'm trying to make my
app damned-fool proof.

Signature
Ed Jay (remove M to respond by email)
Randy Webb - 31 Dec 2005 16:37 GMT
Ed Jay said the following on 12/30/2005 11:13 PM:
>>Ed Jay said the following on 12/30/2005 3:38 PM:
>>
[quoted text clipped - 27 lines]
> the page doesn't get loaded until I exit the script. I am/was looking for
> a way around it.
You can't as you have no access to the cache (if it even exists). You
could look into a Frame situation where one frame kept track of the
"state" of the application and the other Frame was the pages being loaded.
When each page of the form was loaded, check the stateFrame to see what
it is supposed to do and then modify the Submit button accordingly.
<snip>
> Yes, I could provide instructions to not do it, but I'm trying to make my
> app damned-fool proof.
Fool-proof on the web is impossible :)

Signature
Randy
comp.lang.javascript FAQ - http://jibbering.com/faq & newsgroup weekly
Javascript Best Practices - http://www.JavascriptToolbox.com/bestpractices/
Ed Jay - 31 Dec 2005 16:59 GMT
>Ed Jay said the following on 12/30/2005 11:13 PM:
>>
[quoted text clipped - 44 lines]
>Fool-proof on the web is impossible :)
:-)
What I ended up doing was create a hidden input element and setting its
value after validating the form. On resubmitting the form after editing
the page, it tests the value. Iff it's true, it changes the submit URL to
point to the final page.

Signature
Ed Jay (remove M to respond by email)