Posted by Tim Streater on 07/07/07 16:33

In article <Xns9965AD4EB7579arbpenyahoocom@69.28.186.121>,
Adrienne Boswell <arbpen@yahoo.com> wrote:

> Gazing into my crystal ball I observed Tim Streater

[snip]

> Actually, that all is very important. Browsers do different things when
> required attributes are missing.

Even in terms of rendering, you mean?

> Both action and method are required attributes.

Hmm, I understood action to be optional. And that without it, the
default action was that the same form reloaded. Additionally, I could
well want to go to different places depending on the button pushed or
the data that the form passes off to some Javascript. I don't want to
show an action that will never be taken - that just confuses whoever
follows me on the code. I could imagine something like <form
action="none" ... > to make this explicit but can;t recall ever having
seen such an option.

> >> So, now my question becomes - what the heck are you trying to do
> >> here? None of these forms have actions or methods. No names for the
> >> input elements, so no way to send name/value pairs.
> >
> > You do know what the word "example" means, do you? None of your
> > foolish comments are germane to the issue.
>
> I suggest you read the specs then. I also suggest next time you supply a
> URL.

Difficult to do from home, as it happens.

> > Oh gee, no action attribute for the form? No method? No names to the
> > input elements? No action script for the buttons? Well duh! Silly me!
> > I guess the HTML and Javascript books on my desk aren't meant to be
> > doorstops after all.
>
> By your original post, no one knows whether or not you know if these
> things are required or not -- again, another good reason to supply a URL.

Yes, I see that - but I did try to emphasise that I had cut down the
example to the minimum required to demonstrate my problem. I have seen,
in other groups, people post 1000 lines of code and ask why it doesn't
work, with no explanation, and having done no work to isolate the
matter. In my experience, working to isolate the problem makes most of
them obvious.

Having spent a couple of hours late at work reading my HTML/JS books
yesterday and making a simple example, I then continued at home. Only
there did I notice that I had inadvertently left out a </form> in one
place. Putting that back changed things. This was the point at which,
with a concise example behaving in a loopy fashion, that I sought
assistance.

[Back to original message]