whatwg

The minor issue from node-fetch/node-fetch#1569.

Currently it sends Host header as the last header. (If a user did not add it manually)

I think it should send Host header as the first header like it browsers and other libraries do.

Prepend it instead of appending.

"node-fetch": "3.2.3"

A body element's start tag may be omitted if the element is empty, or if the first thing inside the body element is not [ASCII whitespace](https://infra.spec.whatwg.org/#ascii-white

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) (#26159)
• root element without `

The current fetch spec says that all blob: URL requests should result in a 200/OK response (a separate issue, it should probably also mention how to reply if the URL's blob url entry is null). That doesn't entirely match at least chrome's implementation though. In chrome we also support range requests on blob URLs, as long as the range consists of a single range. In that case we reply with a 206 a

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

We have some code that looks like: if (rule instanceof CSSMediaRule) { which fails in happy-dom - I'm assuming this global needs to be defined?

This doesn't make any sense to me: "The behavior when a string value that is not one a valid enumeration value is used when assigning to an attribute, or passed as an operation argument, whose type is the enumeration, is language binding specific."

I believe the word "one" should not have been there.

While implementing lycheeverse/lychee#480 I realized how slow the default emitter really is. It makes link extraction 10-40% slower than html5ever. It is currently not really possible to beat html5ever at all unless a custom emitter is implemented.

We could:

• build another emitter that reuses strings, and calls a callback with borrowed strings instead. Therefore mu

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

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

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