whatwg

From time to time i see ppl using data instead of body which is wrong.
happened just recently in node-fetch/node-fetch#481 (comment)

how do you feel about adding a little warning message that can only appear once. (kinda like node reports that you are using experimental apis)

if ('data' in bodyInit && notWarned) {
  console.warn('use body i

Looking at sticky activation it seems to be calling current high resolution time without a global (that is needed in order to know the time origin).

It'd be good to pass along the global. (W or window, if I'm reading the algorithms correctly)

fd = new FormData
fd.set('a', new Blob)
fd.get('a') === fd.get('a') // false in chromium - true in FF & Safari (don't have IE on Mac)

Looks like there is no test to cover this senario: https://github.com/web-platform-tests/wpt/blob/e45a9f9e65d039c76817ee2a6a1ef02c9311a1cb/xhr/formdata/set-blob.any.js

Presumably these should result in a network error. The current specification doesn't state anything and it's not tested either.

See the README for instructions on where to add tests. In the specification the "blob" case of https://fetch.spec.whatwg.org/#scheme-fetch needs updating to handle current URL’s blob URL entry being null.

Under point 6 of the list of steps to take to "ensure pre-insertion validity", as part of an attempt to implement a procedure involving the particular list of steps, I am having trouble unambiguously interpreting the following statement:

parent has an element child, child is a doctype, or child is non-null and a do

https://url.spec.whatwg.org/commit-snapshots/2ce49383db3506a3c1a527a775693af1100198ef/#host-parsing

5. If input is the empty string, then return 0.

IPv4 parser calls IPv4 number parser in Step 6.2:

2. Let result be the result of parsing part.       <-- call to IPv4 number parser
3. If result is failure, then return input.
4. If result[1] is tr

In https://mimesniff.spec.whatwg.org/#parsing-a-mime-type the following step might be clearer if it explicitly said the trailing sequence after " was to be discarded. Might also be better if the example contains a ';' since the step mentions ';'

Current:

Collect a sequence of code points that are not U+003B (;) from input, given position.
Example: Given text/html;charset="shift_jis"iso-20

In https://infra.spec.whatwg.org/#code-points you suggest.

...Documents using the Infra Standard are encouraged to follow code points by their name...

but you fail to do so, when in https://infra.spec.whatwg.org/#strings you write

To convert a string into a scalar value string, replace any surrogates with U+FFFD.

It should be

To convert a string into a scalar value string, repla

https://github.com/whatwg/whatwg.org/blob/master/resources.whatwg.org/standard.css#L168

A <dl class="switch"> in specs represents a switch statement in programming languages. For stylistic reasons we use an arrow character as generated content before each dt.

Example: https://dom.spec.whatwg.org/#dom-node-nodetype

This renders as "rightwards arrow with hook" in screen readers, accor