What is the issue with the Infra Standard?
Several specs seem to create a promise without defining what "promise" is, e.g. https://html.spec.whatwg.org/#dom-img-decode
Let promise be a new promise.
Most of them eventually return and expose it via Web IDL Promise, which is defined as a JS Promise. But if we start to use it internally in the spec, like whatwg/fullscreen#251 and w3c/screen-orientation#269 intend to do (and like Streams does all over its internal slots), things are less clear what those promises are intended to be.
Having an infra definition referring to JS Promise would be helpful for that.
What is the issue with the Infra Standard?
Several specs seem to create a promise without defining what "promise" is, e.g. https://html.spec.whatwg.org/#dom-img-decode
Most of them eventually return and expose it via Web IDL
Promise, which is defined as a JS Promise. But if we start to use it internally in the spec, like whatwg/fullscreen#251 and w3c/screen-orientation#269 intend to do (and like Streams does all over its internal slots), things are less clear what those promises are intended to be.Having an infra definition referring to JS Promise would be helpful for that.