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)

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 `

processRequestBodyChunk or even processRequestBodyChunkSize would be more representative and either of those would make it clear it's different from processResponseBody, which is only invoked once and is actually passed a response.

Thanks to Tab for making me realize this.

Marking this as a good first issue as it is somewhat straightforward to rename this in various places, but note that thi

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

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.

https://github.com/whatwg/infra/blob/93235624046ab39b2dd880d4091447cc8d0b84d5/infra.bs#L521

The link-text makes it look like there are things called "for lists". I suggest moving the "for" outside the link:

<dd><p>As defined for <a for=list lt="for each">lists</a> (and derivatives) and ...

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