node-fetch currently completely ignoring Content-Length header while consuming response.
Fetch specification about handling Content-Length on server response says almost nothing:
https://fetch.spec.whatwg.org/#concept-http-network-fetch (see whatwg/fetch#67)

On other hand, we have a fetch-node specific extension to limit the size of the response.

My prop

cc @mikewest @annevk @ericlaw1979

From https://html.spec.whatwg.org/multipage/system-state.html#normalize-protocol-handler-parameters:

'If the resulting URL record's scheme is not "https" or the resulting URL record's origin is not same origin with environment's origin, then throw a "SecurityError" DOMException.'

It seems this forbids localhost URLs like http://127.0.0.1 that are in a se

Relevant spec sections:

https://drafts.csswg.org/selectors-4/#the-dir-pseudo
https://html.spec.whatwg.org/multipage/semantics-other.html#selector-ltr

The interesting cases to test are from the definition of "directionality" in HTML:
https://html.spec.whatwg.org/multipage/dom.html#the-directionality

• element with dir="ltr" matches :dir(ltr)
• root element without dir attr

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

What should be the result of new URL("#")?
Browsers return different results.

In my understanding is that new URL("#") should throw a validation error.

1. scheme start state
   1. [skip] If c is an ASCII alpha, append c, lowercased, to buffer, and set state to scheme state.
   2. [match] Otherwise, if state override is not given,

https://notifications.spec.whatwg.org/#dom-serviceworkerregistration-getnotifications is manipulating and ES array in parallel steps. It says things like "push that object to objects". How is that supposed to work? Is that using Array.prototype.push? If so, is it using the initial value of that? Even if it does, that can be affected by accessor properties on Array.prototype and in particu

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