[whatwg] Form data append behavior on null type

[Tingan Ho]

>
> The specification, through the use of Web IDL, requires that "null" be
> sent.  Unless there is a clear majority of implementations that send "", I
> don't think we should change from the default stringification behaviour.


Right now, Chrome, Firefox, Opera uses emtpy strings *""*. Safari and IE
uses null string *"null".*

I think if I send this issue to Safari and IE, they will reply that the W3C
standard doesn't say anything about the behavior. And they will keep using
their implementation.

And that all browser vendors use their own implementation is a nightmare
for the developer. So this problem will be there until a standard is
applied.


On Tue, Dec 31, 2013 at 1:27 PM, Cameron McCormack <cam at mcc.id.au> wrote:

> (Sorry was having mail server trouble before sending you the direct copy.)
>
>
> -------- Original Message --------
> Subject: Re: [whatwg] Form data append behavior on null type
> Date: Tue, 31 Dec 2013 16:17:54 +1100
> From: Cameron McCormack <cam at mcc.id.au>
> To: Tingan Ho <tingan at p1.cn>
> CC: WHATWG <whatwg at lists.whatwg.org>
>
> Tingan Ho wrote:
>
>> Wouldn't it be good to specify the behavior of type null in *append*
>> method
>> of Form data?
>>
>> Right now Safari sends string* "null".* Chrome sends empty string "". I
>> think Chrome's implementation is more right, because in a html form you
>> can't send null value, just empty strings
>>
>> http://www.w3.org/TR/XMLHttpRequest2/#the-append-method
>>
>
> The specification, through the use of Web IDL, requires that "null" be
> sent.  Unless there is a clear majority of implementations that send "",
> I don't think we should change from the default stringification behaviour.
>
>


-- 
Sincerely,

Tingan Ho
tingan at p1.cn