-
Notifications
You must be signed in to change notification settings - Fork 42
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
Promises resolution not defined #463
Comments
Also we should add the promise resolved value in the definition, changing:
by
|
Currently, when a promise is not returning a specific value we just return |
Here is the w3c best practices guide on promises: https://www.w3.org/2001/tag/doc/promises-guide
|
Correct, 7.4 has examples as such:
|
Looks better. |
Several methods of the ORTC objects return a promise, but it is not defined when they are resolved nor what value is it resolved to.
For example:
It is assumed that the the promise will be resolved on async-3 step with an
undefined
(?) value, but this should be explicitly said, as for example:The text was updated successfully, but these errors were encountered: