-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Observable #945
Comments
cc @codehag |
The proposal is very complicated, so this will need some time to consider. For example, which all problems will microtask scheduled event handling cause. And does it solve the problems we want to solve. |
Thanks for the reply. Just to note, the microtask "issue" is only relevant for the Promise-returning operators: https://wicg.github.io/observable/#promise-returning-operators. To aid your analysis on this portion of the proposal, it would probably be useful to check out some of the previous discussion where we detail why this shouldn't be much of an issue at all, and why it makes sense (there are a lot of issues/threads so I wanted to just surgically point you to some of the most relevant discussion on that topic in particular). However I'll note that nothing is set in stone yet, so we'd love more engagement on this if you or other have strong opinions one way or another, to help shape this API surface. |
Request for Mozilla Position on an Emerging Web Specification
@
-mention GitHub accounts): @domfarolinoOther information
This is a new object data type. It also has extensions to the event interface. It was discussed at the most recent TPAC. Chrome has an implementation for evaluation.
The text was updated successfully, but these errors were encountered: