Darien Maillet Valentine

@dcrousso the property [[Get]] order, as bzbarsky mentioned, does expose the inheritance chain to ES code. Within a single "tier", keys are sorted lexically, but the access order is one-tier-at-a-time....

I think this is a great idea, though I realized after looking at some places in our codebase where we’re doing “isAbortError” checks that it seems like it might be...

Right — so the if-statement “artifact” gets moved up, but hasn’t actually gone away. And although that example doesn’t illustrate it cause it was 1:1, it multiplies it, too —...

> you generally don't want to ignore timeouts for a fetch That's consistent with our experience. Timeout is a result. We do actually have checks like this in other cases,...

> Should promise getters be required to use [NewObject]? Was this meant to say [SameObject]? [NewObject] is only defined for operations and I assumed this was because that behavior is...

Both of these extended attributes are a bit odd in that they are "pure" annotations describing high level API behavior. They have no corresponding effects in any Web IDL algorithms....

That makes sense. The distinction I meant to highlight was that they describe universal properties of the operation/attribute behavior itself. Contrast e.g. PutForwards, which is defined only in terms of...

I’m curious whether use of multiple AbortSignals has been considered? That’s how I’ve ended up handling similar cases in userland generally and it permits assurances / control flow that an...

> Not familiar with AbortSignals. Could you provide reference or example, please? [AbortController & AbortSignal](https://dom.spec.whatwg.org/#aborting-ongoing-activities) are the web platform’s generic cancellation primitives. Some examples of their use in other specs:...

Yeah, the spooky-action-at-a-distance — that any terminal literal appearing in the syntactic grammar is implicitly excised from the set of strings belonging to any of the regexp-defined terminal languages —...