From 8941608b3d7ac80b02b4928d0063bdd9927670bd Mon Sep 17 00:00:00 2001 From: Anne van Kesteren Date: Wed, 11 Oct 2017 11:16:11 +0200 Subject: [PATCH] Acknowledge Yehuda Katz Yehuda contributed a lot to the early discussions around the fetch() API. (Also cleanup a couple of references.) Closes #611. --- fetch.bs | 26 ++++++++++++-------------- 1 file changed, 12 insertions(+), 14 deletions(-) diff --git a/fetch.bs b/fetch.bs index 07540b480..40ea7e37a 100644 --- a/fetch.bs +++ b/fetch.bs @@ -24,9 +24,6 @@ Translate IDs: typedefdef-bodyinit bodyinit,dictdef-requestinit requestinit,type
-url:https://xhr.spec.whatwg.org/#concept-formdata-entry;spec:xhr;type:dfn;
-    text:entry
-    text:entries
 url:https://tools.ietf.org/html/rfc7230#section-3.1.1;text:method;type:dfn;spec:http
 url: https://tools.ietf.org/html/rfc7230#section-3.2;text:field-name;type:dfn;spec:http
 url: https://tools.ietf.org/html/rfc7230#section-3.2;text:field-content; type:dfn;spec:http
@@ -4733,16 +4730,16 @@ runs the associated steps:
     Returning Values from Forms: multipart/form-data. [[!RFC7578]]

Each part whose `Content-Disposition` header contains a `filename` - parameter must be parsed into an entry whose value is a {{File}} whose content is the - content of the part. The {{File/name}} attribute of the {{File}} must have the value of the - `filename` parameter of the part. The {{Blob/type}} attribute of the {{File}} must - have the value of the `Content-Type` header of the part if the part has such - header, and `text/plain` (the default defined by [[!RFC7578]] section 4.4) - otherwise.

+ parameter must be parsed into an entry whose value is a {{File}} object + whose contents are the contents of the part. The {{File/name}} attribute of the {{File}} object + must have the value of the `filename` parameter of the part. The {{Blob/type}} + attribute of the {{File}} object must have the value of the `Content-Type` header + of the part if the part has such header, and `text/plain` (the default defined by + [[!RFC7578]] section 4.4) otherwise.

Each part whose `Content-Disposition` header does not contain a - `filename` parameter must be parsed into an entry whose value is the - UTF-8 decoded content of the part. This is done regardless of the + `filename` parameter must be parsed into an entry whose value + is the UTF-8 decoded content of the part. This is done regardless of the presence or the value of a `Content-Type` header and regardless of the presence or the value of a `charset` parameter.

@@ -4753,8 +4750,8 @@ runs the associated steps:
  • If that fails for some reason, then throw a TypeError. -

  • Return a new {{FormData}} object, appending each entry, resulting from the parsing - operation, to entries. +

  • Return a new {{FormData}} object, appending each entry, resulting from + the parsing operation, to entries.

    The above is a rough approximation of what is needed for @@ -4777,7 +4774,7 @@ runs the associated steps:

    Otherwise, throw a TypeError.

    JSON -

    Return the result of running parse JSON with bytes on bytes. +

    Return the result of running parse JSON from bytes on bytes.

    text

    Return the result of running UTF-8 decode on @@ -6210,6 +6207,7 @@ Vignesh Shanmugam, Vladimir Dzhuvinov, Wayne Carr, Xabier Rodríguez, +Yehuda Katz, Yoav Weiss, Youenn Fablet, 平野裕 (Yutaka Hirano), and