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 20758 - remove() should be an asynchronous operation
Summary: remove() should be an asynchronous operation
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: Media Source Extensions (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Adrian Bateman [MSFT]
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-01-24 16:17 UTC by Adrian Bateman [MSFT]
Modified: 2013-01-31 00:47 UTC (History)
3 users (show)

See Also:


Attachments

Description Adrian Bateman [MSFT] 2013-01-24 16:17:10 UTC
There may be a large amount of work to do to process a remove() operation and we should not block the UI thread while this happens.

Proposed Change: expand the "append" related events and attribute for the remove operation

- Section 4: rename "appending" attribute to "updating" through the whole section
- Section 4: rename "appendstart" to "updatestart" through the section
- Section 4: rename "appendend" to "updateend" through the section 
- Section 4.1: in the updating definition, add "remove()" operation to the list
- Section 4.2: in the definition of the remove() operation insert the following between steps 4 and 5
   o Set the updating attribute to true.
   o Queue a task to fire a simple event named updatestart at this SourceBuffer object.
- Then after step 5.4, add the following
  o Set the updating attribute to false.
  o Queue a task to fire a simple event named updateend at this SourceBuffer object.
Comment 1 Aaron Colwell (c) 2013-01-31 00:47:57 UTC
Changes committed
https://dvcs.w3.org/hg/html-media/rev/b35722b0cd8f