Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.php > #2373
| From | "Peter H. Coffin" <hellsop@ninehells.com> |
|---|---|
| Newsgroups | comp.lang.php |
| Subject | Re: multi-page form |
| Date | 2011-06-28 13:57 -0500 |
| Organization | A noiseless patient Spider |
| Message-ID | <slrnj0k907.207.hellsop@nibelheim.ninehells.com> (permalink) |
| References | <iuabqa$530$1@dont-email.me> <iuasu2$6lc$1@dont-email.me> <iuaujv$c7t$1@dont-email.me> |
On Mon, 27 Jun 2011 18:01:21 -0400, William Gill wrote:
> There are as few as 4 or 5 fields on some pages, but they may need/want
> to back up to see their earlier input.
>
> All I want is to prevent them from completing some fields; then backing
> up and losing their input.
>
> I'm thinking of creating an XMLHttpRequest object and using it to
> update session variables if a user backs up (triggered by the ONUNLOAD
> event),and then repopulating the fields when he/she returns (ONLOAD).
>
> Haven't done it in a while, and wanted to know if this is the best approach.
If the circumstance you're concerned about is (for example) a 3-page
form, a user being on page 2, entering data in a few fields, flipping
back to page one, flipping forward to page 2 again and the concern is
about whether the previous page-2 fields still have the entered data or
not, don't worry about it. It's all under the brower's control anyway.
If the user uses the page-forward button, the entered data will
*probably* still be there, but there's nothing you can do to control it
either way. If the user uses the "next page"/html submit button to go
forward, the entered data will probably *not* be there, but in this
case, you *still* can't do anything about it. And we're not even getting
into the whole molassas vat of what happens if the user changes
something and then uses those two different means of navigation...
Even the use of the javascript events doesn't necessarily fix the
behavior to one thing or the other, as web pages are *supposed to be*
fairly agnostic as to user agent. Not all user agents have javascript,
not all have it turned on, not all have complete implementations of
those events even if they do. (EG: some versions of Firefox trigger
.unload on a tab close, and trigger .load on a tab restore. Some don't.)
Short answer: PHP can't make a browser into a complex client interface
engine. It just won't work. Can't make a silk purse out of a pig's ear
either.
--
29. I will dress in bright and cheery colors, and so throw my enemies
into confusion.
--Peter Anspach's list of things to do as an Evil Overlord
Back to comp.lang.php | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
multi-page form William Gill <noreply@domain.invalid> - 2011-06-27 12:40 -0400
Re: multi-page form Bill B <me@privacy.net> - 2011-06-27 13:31 -0400
Re: multi-page form William Gill <noreply@domain.invalid> - 2011-06-27 13:41 -0400
Re: multi-page form Bill B <me@privacy.net> - 2011-06-27 14:24 -0400
Re: multi-page form Jerry Stuckle <jstucklex@attglobal.net> - 2011-06-27 17:32 -0400
Re: multi-page form William Gill <nospam@domain.invalid> - 2011-06-27 18:01 -0400
Re: multi-page form Bill B <me@privacy.net> - 2011-06-27 18:18 -0400
Re: multi-page form Graham Hobbs <ghobbs@cdpwise.net> - 2011-07-05 20:06 -0400
Re: multi-page form Jerry Stuckle <jstucklex@attglobal.net> - 2011-06-27 18:54 -0400
Re: multi-page form William Gill <nospam@domain.invalid> - 2011-06-28 04:22 -0400
Re: multi-page form Jerry Stuckle <jstucklex@attglobal.net> - 2011-06-28 06:53 -0400
Re: multi-page form William Gill <nospam@domain.invalid> - 2011-06-28 12:13 -0400
Re: multi-page form Bill B <me@privacy.net> - 2011-06-28 14:00 -0400
Re: multi-page form Jerry Stuckle <jstucklex@attglobal.net> - 2011-06-28 15:02 -0400
Re: multi-page form Bill B <me@privacy.net> - 2011-06-28 15:06 -0400
Re: multi-page form Bill B <me@privacy.net> - 2011-06-28 15:46 -0400
Re: multi-page form William Gill <nospam@domain.invalid> - 2011-06-28 16:05 -0400
Re: multi-page form Bill B <me@privacy.net> - 2011-06-28 16:12 -0400
Re: multi-page form Bill B <me@privacy.net> - 2011-06-28 16:20 -0400
Re: multi-page form Jerry Stuckle <jstucklex@attglobal.net> - 2011-06-28 18:58 -0400
Re: multi-page form Jeff North <jnorthau@yahoo.com.au> - 2011-06-29 09:30 +1000
Re: multi-page form Jerry Stuckle <jstucklex@attglobal.net> - 2011-06-28 20:21 -0400
Re: multi-page form Jeff North <jnorthau@yahoo.com.au> - 2011-06-29 14:52 +1000
Re: multi-page form Jerry Stuckle <jstucklex@attglobal.net> - 2011-06-29 07:59 -0400
Re: multi-page form Bill B <me@privacy.net> - 2011-06-29 08:09 -0400
Re: multi-page form Jerry Stuckle <jstucklex@attglobal.net> - 2011-06-29 08:41 -0400
Re: multi-page form Bill B <me@privacy.net> - 2011-06-29 08:48 -0400
Re: multi-page form Jerry Stuckle <jstucklex@attglobal.net> - 2011-06-29 11:08 -0400
Re: multi-page form Bill B <me@privacy.net> - 2011-06-29 12:27 -0400
Re: multi-page form Jeff North <jnorthau@yahoo.com.au> - 2011-06-29 23:10 +1000
Re: multi-page form Jerry Stuckle <jstucklex@attglobal.net> - 2011-06-29 11:09 -0400
Re: multi-page form Michael Fesser <netizen@gmx.de> - 2011-06-29 18:56 +0200
Re: multi-page form Jerry Stuckle <jstucklex@attglobal.net> - 2011-06-29 15:32 -0400
Re: multi-page form "Peter H. Coffin" <hellsop@ninehells.com> - 2011-06-28 13:57 -0500
Re: multi-page form Jeff North <jnorthau@yahoo.com.au> - 2011-06-29 08:46 +1000
Re: multi-page form William Gill <nospam@domain.invalid> - 2011-06-28 19:29 -0400
Re: multi-page form Jeff North <jnorthau@yahoo.com.au> - 2011-06-29 15:15 +1000
Re: multi-page form Jerry Stuckle <jstucklex@attglobal.net> - 2011-06-29 08:01 -0400
Re: multi-page form Michael Fesser <netizen@gmx.de> - 2011-06-29 19:00 +0200
Re: multi-page form Michael Fesser <netizen@gmx.de> - 2011-06-29 19:05 +0200
Re: multi-page form William Gill <nospam@domain.invalid> - 2011-06-29 13:44 -0400
csiph-web