Closed Bug 1547637 Opened 6 years ago Closed 6 years ago

[wpt-sync] Sync PR 16432 - Same events at the same time don't replace each other

Categories

(Core :: Web Audio, defect, P4)

Product:
Core
Component:
Web Audio
Type:
defect

Tracking

()

Status:
RESOLVED FIXED
Milestone:
mozilla69
Tracking Flags:
Tracking Status
firefox69 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream])

Sync web-platform-tests PR 16432 into mozilla-central (this bug is closed when the sync is complete).

PR: https://github.com/web-platform-tests/wpt/pull/16432
Details from upstream follow.

Raymond Toy <rtoy@chromium.org> wrote:

Same events at the same time don't replace each other

Previously, if multiple events of the same type were scheduled at the
same time, then each new event would replace the existing event. This
is incorrect according to the spec. There is no special treatment
here and events are inserted in the order in which they're received.

This change only affects linear and exponential ramps. The result is
that the ramp preceeds up to the first event value, and then at the
event time, the output instantly jumps to the last event value.

Bug: 925037
Test: the-audioparam-interface/event-insertion.html updated
Change-Id: I2de32c7a71c12e5673b2db8cf81f9dc48f3ee458
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1577661
Reviewed-by: Hongchan Choi \<hongchan@chromium.org>
Commit-Queue: Raymond Toy \<rtoy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#654242}

Component: web-platform-tests → Web Audio
Product: Testing → Core
Failed to get results from try push
Pushed by james@hoppipolla.co.uk: https://hg.mozilla.org/integration/mozilla-inbound/rev/e74bcf760cea [wpt PR 16432] - Same events at the same time don't replace each other, a=testonly

https://hg.mozilla.org/mozilla-central/rev/e74bcf760cea

Status: NEW → RESOLVED
Closed: 6 years ago
status-firefox69: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla69
You need to log in before you can comment on or make changes to this bug.