Update Chrome/Firefox notes for AudioParam.value
#25212
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
data:api
hamishwillee
commented
Nov 26, 2024
8 tasks
caugner
requested changes
Nov 26, 2024
caugner
changed the title
AudioParam.value
caugner
approved these changes
Nov 27, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
FF134 brings
AudioParam.valueto spec compliance by always setting it to the defaultValue, rather than ignoring the setter if there happens to be a scheduled event when the setter is called, in https://bugzilla.mozilla.org/show_bug.cgi?id=1308435The spec change is here WebAudio/web-audio-api@73c2b88#diff-0eb547304658805aad788d320f10bf1f292797b5e6d745a3bf617584da017051R2889
According to the issue it breaks a lot of tests but is unlikely to break much real code.
Anyway, this adds a note to the FF release, It also adds a compat note to the Chrome release that was pulled out of the docs.
Related docs work can be tracked in mdn/content#36916