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
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
this problem will be there until a standard is
applied.
On Tue, Dec 31, 2013 at 1:27 PM, Cameron McCormack c...@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
On 12/31/13 1:44 AM, Tingan Ho wrote:
Right now, Chrome, Firefox, Opera uses emtpy strings **. Safari and IE
uses null string *null.*
May I ask which Firefox version you tested? I would think that Firefox
20 and newer would be sending null here, and testing on
http://jsfiddle.net/fbgLg/
May I ask which Firefox version you tested? I would think that Firefox 20
and newer would be sending null here, and testing on
http://jsfiddle.net/fbgLg/ suggests that I think correctly.
Hi Boris, my bad, you where right Firefox is sending null.
On Tue, Dec 31, 2013 at 3:01 PM, Victor
