This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 26224 - SourceBuffer.endOfStream() behavior undefined for empty, null, or garbage 'error' parameter.
Summary: SourceBuffer.endOfStream() behavior undefined for empty, null, or garbage 'er...
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: Media Source Extensions (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Adrian Bateman [MSFT]
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-06-27 18:22 UTC by Jer Noble
Modified: 2014-06-27 20:49 UTC (History)
3 users (show)

See Also:

Attachments

Description Jer Noble 2014-06-27 18:22:11 UTC 
The behavior of the '2.2 endOfStream()' method is undefined in the case where the 'error' parameter is not either undefined, 'network', or 'decode'.

The test suite being developed by acolwell asserts that 'error' parameters not matching the above should throw a TypeError, and should not modify the SourceBuffer.readyState, but this asserts behavior not in the spec.
Comment 1 Aaron Colwell 2014-06-27 20:44:04 UTC 
These cases are covered by enumeration behavior defined in the WebIDL spec (http://www.w3.org/TR/WebIDL/#es-enumeration)
Comment 2 Jer Noble 2014-06-27 20:49:54 UTC 
Thanks for the pointer.