Darien Maillet Valentine

> This is coming up now because in blink we're [trying](https://groups.google.com/a/chromium.org/g/blink-dev/c/j7vOAkMbu_M/m/OmlnogDoAgAJ?utm_medium=email&utm_source=footer) to expose the [Report interface](https://w3c.github.io/reporting/#idl-index) and needing to do a bunch of web compat analysis to figure out whether...

> We exposed Report only on Nightly before, ... Apologies, was remembering the particulars of that issue wrong.

Likewise it should not permit `sequence`, `record`, `ObservableArray`, or (at least not without additional requirements) `Promise`, nor annotated or nullable types with these inner types. I think this is an...

> I don't understand why we'd restrict promises from being held by these types. I was thinking that in the absence of a definite use case, the added complexity of...

> In some sense, a Promise is just another interface (used to be), with no requirement to act one way or another. The Web IDL `Promise` type does have an...

That AbortController/AbortSignal unifies cancellation is its most important property. Right now people are mainly familiar with AC because of fetch, but the key to its effective use is to make...

Operations have had new parameters added previously many times, right? Is there something that makes the variadic case more hazardous? If the hazard is that someone might have passed an...

> it is not going to be immediately apparent why the "xyz" is not showing up That’s a good point. I have no strong preference myself for expanded signature vs...

> doesn't allow for class fields or constructor initialisation logic in the signal Return override permits this. ```js class WatchSignal extends function(o) { return Object.setPrototypeOf(o, new.target.prototype); } { #fields =...

I figured this was intentional because the concept of boolean presence vs absence content attributes is HTML-specific, not an XML thing, no? (I’d actually find this addition useful given the...