No! NO! NO! ... If the NAME aattribute is specified, then the name
value pair must be sent to the server as part of the request when
a SUBMIT button is clicked and for reset, a name has NO semantic
meaning. THis could cause currently conforming and working
applications to suffer grief.
I see that, but I still feel that we are causing authors and would-be
authors more problems by making NAME optional.
For SUBMIT, I can see a good reason for specifically _wanting_ a name
to be sent, when you have multiple optional SUBMIT fields (which I
thought the DTD allowed).
For RESET, this action doesn't cause any send or receive activity, so
the presence of a name should not be relevant, should it?
///Peter, feeling fuzzy at 2.30am