- From: <bugzilla@jessica.w3.org>
- Date: Tue, 16 Jun 2015 18:58:26 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28822 Bug ID: 28822 Summary: [MSE] Spec is ambiguous as to event behavior of an explicit MediaSource duration of +Infinity Product: HTML WG Version: unspecified Hardware: PC OS: All Status: NEW Severity: normal Priority: P2 Component: Media Source Extensions Assignee: wolenetz@google.com Reporter: bobbyholley@gmail.com QA Contact: public-html-bugzilla@w3.org CC: bugs+w3@karlt.net, jdsmith@microsoft.com, jyavenard@mozilla.com, mike@w3.org, public-html-media@w3.org "Update the media controller duration to new duration and run the HTMLMediaElement duration change algorithm." By my reading, the specs are currently ambiguous as to what happens when the MediaSource.duration gets set to +Infinity. Do we fire durationchange or not? mediasource-duration-boundaryconditions.html tests that we do, but the HTML5 spec uses +Infinity to denote "unknown duration", and we're only supposed to fire durationchange when the duration changes "to a known value". Should +Infinity have a different meaning when it comes from MediaSource? -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Tuesday, 16 June 2015 18:58:28 UTC