|
Posted by Alan J. Flavell on May 25, 2005, 12:42 pm
Please log in for more thread options
On Wed, 25 May 2005, RobG wrote:
> Alan J. Flavell wrote:
> > On Tue, 24 May 2005, Jim Moe wrote:
> >
> > > My experience is that you get the contents of the text box that is last
> > > defined with a given name. None of the others show up.
> >
> > Then you have an incomplete server-side implementation, but this is
> > off-topic for the HTML authoring group.
>
> I disagree with that. If the OP is serving invalid HTML
I still see no evidence that the OP needs to serve "invalid" HTML to
achieve this.
> text elements with duplicate names, browser behaviour is not defined
> and you can't be certain of what will be returned to the server.
The behaviour is defined in
http://www.w3.org/TR/html4/interact/forms.html#form-data-set
If two "successful controls" have the same name, then the "form data
set" submitted to the server will contain two name=value pairs with
the same name.
That is a specification of the form data set as submitted from the
browser/client to the server. It's not a specification of a software
interface between a server and a server-side process - you'd need to
look elsewhere for that, as I already said.
> > The HTML spec specifies the format of the submitted dataset (as
> > sent from the client to the server). That part is on-topic here.
>
> And what the server sends to the client is irrelevant?
Congratulations, you're arguing against something that I never said.
> > At this point in the procedure the server neither knows nor cares
> > what kind of form control that was. They could easily be of
> > different kinds (e.g a pull-down list and a type-in text box of
> > the same name) if you wanted. Or not, as you choose.
>
> If that was to occur in the same form, then that is invalid HTML
Where's your test document to demonstrate this claimed invalidity?
| 
XML Sitemap