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 27559 - Clarify TrackDefaultList ctor for shallow vs deep copy of trackDefaults parameter
Summary: Clarify TrackDefaultList ctor for shallow vs deep copy of trackDefaults param...
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: Media Source Extensions (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: CR
Assignee: Aaron Colwell
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-12-10 22:50 UTC by Matt Wolenetz
Modified: 2014-12-11 18:49 UTC (History)
3 users (show)

See Also:

Attachments

Description Matt Wolenetz 2014-12-10 22:50:53 UTC 
TrackDefaultList constructor takes a sequence<TrackDefault> parameter named trackDefaults.
After enforcing uniqueness of <type,byteStreamTrackID> within trackDefaults, the spec says to:
"2. Store a copy of trackDefaults in this new object so the values can be returned by the accessor methods."

The spec is unclear whether a shallow or deep copy of the TrackDefault objects within trackDefaults is required.

Since TrackDefault exposes no mutator methods, a shallow copy should suffice (it would not allow apps to violate the <type,byteStreamTrackID> uniqueness constraint previously enforced in the TrackDefaultList ctor.)

The type of copy is app-visible, hence this bug to clarify the spec.