Posted by Alan J. Flavell on 01/23/06 22:07

On Mon, 23 Jan 2006, Jonathan N. Little wrote:

> Alan J. Flavell wrote:
>
> > On Mon, 23 Jan 2006, Jonathan N. Little wrote:
> >
> > > Travis Newbury wrote:
> > >
> > > > Leszek wrote:
> > > >
> > > > > I tried something like this:
> > > > > <input type="button" value="<<Back" onclick="history.back()"/>
> > > > > and it works with my browser
> > > > > But is the input type="button" working with all browsers?
> >
> > RTFM.
>
> Do you mean me?

Follow the quote marks?

> > > The way I did it was to have one PHP script handle all pages of the
> > > multipage form, then for each page I had two submit buttons...
> > >
> > > #on Page 1
> > > <input type="submit" name="back0" value="<<Back">
> >
> > [...]
> >
> This has absolutely *nothing* to do with JavaScript!

Then it's even more confusing to refer to "Back", since your
server-side process has no real idea what's on the browser's history
stack.

> Do you seen any 'onclick' or any other event handler in my example?

Only in what you quoted, indeed.

> Again this is server-side!

So it seems that now the user is presented with a browser Back button
that does one thing (that they are presumably familiar with), and an
in-page Back control that does something that they can only guess at.

> But just for your benefit, I do also have JavaScript that attach and
> onclick and onsubmit handlers of *if* JavaScript is available then I
> can pretest and catch errors *before* making a server call...

Now he tells us...

> Again, I chalk this all up to that you misread my post.

Fair comment, but I took your "the way I did it was..." at face value.
In fact, it now seems that you didn't do "it", but something different
- which, with respect, you didn't describe in detail until I
challenged you.

[Back to original message]