Re: submission/@method default

> What is our reasoning for not having a default? I don't see what it buys
> us.
> I would suggest we pick a value, and the two candidates seem to be GET and
> GET because it is the most highly occurring, and POST because it is the
> one that serialises as XML.
> Despite that, I would vote for GET, since it is the simple one (at the
> receiving end).

+1 for defaulting to GET, and it's the default in HTML [1]:

    "The invalid value default for these attributes is the GET state. The
missing value default for the method attribute is also the GET state."

And this was the case with HTML 4 as well. [2]



Received on Wednesday, 30 November 2016 16:56:27 UTC