Closed Bug 1477144 Opened 7 years ago Closed 7 years ago

[wpt-sync] Sync PR 12080 - Use RangeError object instead of 'RangeError'

Categories

(Core :: Web Audio, enhancement, P4)

enhancement

Tracking

()

RESOLVED FIXED
mozilla63
Tracking Status
firefox63 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

Sync web-platform-tests PR 12080 into mozilla-central (this bug is closed when the sync is complete). PR: https://github.com/web-platform-tests/wpt/pull/12080 Details from upstream follow. Raymond Toy <rtoy@chromium.org> wrote: > Use RangeError object instead of 'RangeError' > > Remove expected results too. > > Bug: 865578 > Test: affected tests pass > Change-Id: I897f7d01d7dbcd7d7316457db1ce2e307cee88ed > Reviewed-on: https://chromium-review.googlesource.com/1144139 > WPT-Export-Revision: dc71299b2710bfbaed30ede4540989d66e595eac
Component: web-platform-tests → Web Audio
Product: Testing → Core
Ran 4 tests and 133 subtests OK : 4 PASS : 98 FAIL : 35 New tests that have failures or other problems: /webaudio/the-audio-api/the-audiobuffersourcenode-interface/audiobuffersource-basic.html # AUDIT TASK RUNNER FINISHED: 1 out of 1 tasks were failed.: FAIL < [start/stop exceptions] 4 out of 12 assertions were failed.: FAIL X start(-1) threw "RangeError" instead of EcmaScript error RangeError.: FAIL X start(0,-1) threw "RangeError" instead of EcmaScript error RangeError.: FAIL X start(0,0,-1) threw "RangeError" instead of EcmaScript error RangeError.: FAIL X stop(-1) threw "RangeError" instead of EcmaScript error RangeError.: FAIL /webaudio/the-audio-api/the-audioparam-interface/audioparam-exceptional-values.html X gain.gain.exponentialRampToValueAtTime(-1e-100,1) threw "SyntaxError" instead of EcmaScript error RangeError.: FAIL X gain.gain.exponentialRampToValueAtTime(0,1) threw "SyntaxError" instead of EcmaScript error RangeError.: FAIL X gain.gain.exponentialRampToValueAtTime(1,-1) threw "NotSupportedError" instead of EcmaScript error RangeError.: FAIL X gain.gain.exponentialRampToValueAtTime(1e-100,1) threw "SyntaxError" instead of EcmaScript error RangeError.: FAIL X gain.gain.linearRampToValueAtTime(1,-1) threw "NotSupportedError" instead of EcmaScript error RangeError.: FAIL X gain.gain.setTargetAtTime(1,-1,1) threw "NotSupportedError" instead of EcmaScript error RangeError.: FAIL X gain.gain.setTargetAtTime(1,1,-1) threw "NotSupportedError" instead of EcmaScript error RangeError.: FAIL X gain.gain.setValueAtTime(1,-1) threw "NotSupportedError" instead of EcmaScript error RangeError.: FAIL X gain.gain.setValueCurveAtTime([0,0,0],-1,1) threw "NotSupportedError" instead of EcmaScript error RangeError.: FAIL /webaudio/the-audio-api/the-audioparam-interface/audioparam-method-chaining.html X Calling exponentialRampToValueAtTime() with a zero target value threw "SyntaxError" instead of EcmaScript error RangeError.: FAIL X Calling setValueAtTime() with a negative end time threw "NotSupportedError" instead of EcmaScript error RangeError.: FAIL /webaudio/the-audio-api/the-constantsourcenode-interface/constant-source-basic.html X start(-1) threw "NotSupportedError" instead of EcmaScript error RangeError.: FAIL X stop(-1) threw "NotSupportedError" instead of EcmaScript error RangeError.: FAIL
Pushed by james@hoppipolla.co.uk: https://hg.mozilla.org/integration/mozilla-inbound/rev/d026c6be5fda [wpt PR 12080] - Use RangeError object instead of 'RangeError', a=testonly
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla63
You need to log in before you can comment on or make changes to this bug.