-
Notifications
You must be signed in to change notification settings - Fork 166
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
Clarify language around resuming closed AudioContexts. #1141
Conversation
Also clean up fuzzy assumptions about the AudioContext class being the subject of the section in question (it applies to offline contexts to some extent).
Creating an <a>AudioContext</a> often involves creating a | ||
high-priority thread, and using a low-latency system audio stream, | ||
both having an impact on energy consumption. Creating more than one | ||
<a>AudioContext</a> in a document is most of the time unnecessary. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This PR removes this sentence, is that intentional ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The removal was intentional (the language felt like overstepping) , but perhaps I overdid it. WIll reinstate.
index.html
Outdated
it to continue to operate later by invoking <a href= | ||
"#widl-BaseAudioContext-resume-Promise-void">resume</a>. Closing an | ||
<a>AudioContext</a> completely releases all of its resources, after | ||
which it cannot be used or resumed again. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's allowed to release resources, not mandatory. I'd put something like:
Closing an AudioContext allows implementations to release resources
to put an emphasis on the fact that this is an implementation choice.
@rtoy reminder |
index.html
Outdated
<p> | ||
Constructing or resuming a <a>BaseAudioContext</a> subclass | ||
involves <dfn id="acquiring">acquiring system resources</dfn>. This | ||
means creating a high-priority thread and (for <a>AudioContext</a> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"high-priority thread" isn't required.
index.html
Outdated
involves <dfn id="acquiring">acquiring system resources</dfn>. This | ||
means creating a high-priority thread and (for <a>AudioContext</a> | ||
only) creating a system audio stream. This operation returns when | ||
the audio stream is ready. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we have a concept of "ready" really means? If so, a link to this would be great.
…text “readiness”
index.html
Outdated
system audio stream. This operation returns when the audio stream | ||
is ready. | ||
authors to <dfn id="releasing">release system resources</dfn>, | ||
including threads, processes and audio streams. Suspending an |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"Suspending an" -> "Suspending a"
Fix #1100