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 22116 - AppendWindowEnd behavior
Summary: AppendWindowEnd behavior
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: Media Source Extensions (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Adrian Bateman [MSFT]
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard: PRE_LAST_CALL
Keywords:
Depends on:
Blocks:
 
Reported: 2013-05-21 11:13 UTC by Cyril Concolato
Modified: 2013-06-05 16:13 UTC (History)
3 users (show)

See Also:

Attachments

Description Cyril Concolato 2013-05-21 11:13:32 UTC 
The spec currently says:
"If frame end timestamp is greater than appendWindowEnd, then set the need random access point flag to true, drop the coded frame, and jump to the top of the loop to start processing the next coded frame."

We probably want to compare the "frame presentation timestamp" here and not the "frame end timestamp". If a frame lasts longer than the duration of the append window, you probably don't want to drop it, just shorten its duration.
Comment 1 Aaron Colwell 2013-05-23 18:30:51 UTC 
Marking all pre-Last Call bugs
Comment 2 Aaron Colwell 2013-05-28 17:11:42 UTC 
MSE doesn't allow truncation of coded frames since this may not be possible for hardware decoders to accomplish. The idea is that only frames that are completely inside the append window are added. Ones that overlap the start or end of the window are not admitted.
Comment 3 Aaron Colwell 2013-06-05 16:13:52 UTC 
Resolving as WONTFIX. Please reopen if you believe that it is really worth introducing optional behavior in this regard.