Skip to content
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

Move audioparam-nominal-range test to WPT #28600

Merged
merged 1 commit into from
Apr 20, 2021

Conversation

chromium-wpt-export-bot
Copy link
Collaborator

@chromium-wpt-export-bot chromium-wpt-export-bot commented Apr 20, 2021

The test audioparam-nominal-range verifies that the nominal range
(min/max): of each AudioParam has the specified values, and that
attempts to set the value outside the min/max range clamps the value
to the nominal range.

The behavior is specified here:
https://webaudio.github.io/web-audio-api/#nominal-range

Bug: 1041105
Change-Id: I03f58e3e29aaeff84d764fedd6748fe41baf6eeb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2836870
Reviewed-by: Hongchan Choi <hongchan@chromium.org>
Commit-Queue: Raymond Toy <rtoy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#874293}

Copy link
Collaborator

@wpt-pr-bot wpt-pr-bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The review process for this patch is being conducted in the Chromium project.

The test audioparam-nominal-range verifies that the nominal range
(min/max): of each AudioParam has the specified values, and that
attempts to set the value outside the min/max range clamps the value
to the nominal range.

The behavior is specified here:
https://webaudio.github.io/web-audio-api/#nominal-range

Bug: 1041105
Change-Id: I03f58e3e29aaeff84d764fedd6748fe41baf6eeb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2836870
Reviewed-by: Hongchan Choi <hongchan@chromium.org>
Commit-Queue: Raymond Toy <rtoy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#874293}
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants