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 21150 - Changing duration while updating should fail
Summary: Changing duration while updating should fail
Status: RESOLVED WORKSFORME
Alias: None
Product: HTML WG
Classification: Unclassified
Component: Media Source Extensions (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Aaron Colwell (c)
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-02-28 06:34 UTC by Adrian Bateman [MSFT]
Modified: 2013-03-04 19:39 UTC (History)
3 users (show)

See Also:

Attachments

Description Adrian Bateman [MSFT] 2013-02-28 06:34:10 UTC 
Changing the duration while an append or remove is pending should not be allowed. One specific problem is that reducing the duration relies on a remove operation, which can't be started if we are already in an updating situation.

We think that an INVALID_STATE_ERR exception should be thrown before step 2 in 2.4.6 Duration change.
Comment 1 Aaron Colwell (c) 2013-03-04 17:27:56 UTC 
As far as I can tell, duration changes triggered by the JavaScript are already blocked by pending appends.

- Step 3 on the duration setter algorithm prevents setting during append.(https://dvcs.w3.org/hg/html-media/raw-file/default/media-source/media-source.html#widl-MediaSource-duration)

- The duration change triggered by endOfStream() is protected by Step 2 in that algorithm. (https://dvcs.w3.org/hg/html-media/raw-file/default/media-source/media-source.html#widl-MediaSource-endOfStream-void-EndOfStreamError-error)

I believe all other duration change calls are the result of algorithms run during an append so I believe it should be ok. Am I missing something?
Comment 2 Adrian Bateman [MSFT] 2013-03-04 19:39:37 UTC 
You're right - we missed it just focusing on reviewing the algorithm section.