Open Bug 849636 Opened 10 years ago Updated 3 years ago

Handle invalid offset/duration passed to AudioBufferSourceNode.start the same way that WebKit does

Categories

(Core :: Web Audio, defect, P4)

x86
macOS
defect

Tracking

()

People

(Reporter: ehsan.akhgari, Assigned: padenot)

References

Details

(Whiteboard: [blocking-webaudio-])

Attachments

(2 files)

Attached file Testcase
See the testcase.  I also filed <https://www.w3.org/Bugs/Public/show_bug.cgi?id=21240> to get this properly spec'ed.
Blocks: webaudio
Attached patch Patch (v1)Splinter Review
Assignee: nobody → ehsan
Status: NEW → ASSIGNED
Attachment #723217 - Flags: review?(roc)
Comment on attachment 723217 [details] [diff] [review]
Patch (v1)

Review of attachment 723217 [details] [diff] [review]:
-----------------------------------------------------------------

This behavior doesn't make sense to me. I'll comment in the bug.
Mass moving Web Audio bugs to the Web Audio component.  Filter on duckityduck.
Component: Video/Audio → Web Audio
Assignee: ehsan → nobody
Whiteboard: [blocking-webaudio-]
Priority: -- → P2
Paul - is this bug still valid?
Flags: needinfo?(padenot)
Priority: P2 → --
It is I think.
Flags: needinfo?(padenot)
Priority: -- → P3
Mass change P3->P4 to align with new Mozilla triage process.
Priority: P3 → P4
Assignee: nobody → padenot
You need to log in before you can comment on or make changes to this bug.