You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
No action required, I just want to note that this proposal meets the two requests that were made in TC39 that I was aware of:
@domenic asked that observables tie into a unified concept of cancellation. This proposal meets that with AbortSignal integration.
I asked that this proposal be based on explicit cooperation with DOM/HTML folks, that it not be done by TC39 in a vacuum. This is resolved here, by the explicit integration proposed in this repository. (I was also concerned about the intelligibility of the programming model, which we can discuss in another issue.)
Historically, the proposal was held back in TC39 because no one presented a version which solved both issues--no one put the proposal on the TC39 agenda since 2016. As with cancellation, TC39 did not reject this proposal or deem it out of scope. Anyway, at this point, I'm happy with this proposal proceeding in whichever venue is most convenient for proponents, now that we have WinterCG to bridge the gap between other runtime environments, and an improved culture on all sides of taking more stakeholders' concerns into account.
The text was updated successfully, but these errors were encountered:
I think this issue is a great note — and thank you for filing it. At this point though, I think it can probably be closed. See also the discussion going on in w3ctag/design-reviews#902 about standards venue. I think we are happy with the proposal proceeding along the current path.
No action required, I just want to note that this proposal meets the two requests that were made in TC39 that I was aware of:
Historically, the proposal was held back in TC39 because no one presented a version which solved both issues--no one put the proposal on the TC39 agenda since 2016. As with cancellation, TC39 did not reject this proposal or deem it out of scope. Anyway, at this point, I'm happy with this proposal proceeding in whichever venue is most convenient for proponents, now that we have WinterCG to bridge the gap between other runtime environments, and an improved culture on all sides of taking more stakeholders' concerns into account.
The text was updated successfully, but these errors were encountered: