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 9760 - "It might not be zero if the clip's timeline is not zero-based" - please make startTime start at 0 even for clips that are not zero-based, to make the API simpler to use for authors. If this change is made, startTime seems to be equivalent to buffered.sta
Summary: "It might not be zero if the clip's timeline is not zero-based" - please make...
Status: RESOLVED WORKSFORME
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-18 08:01 UTC by contributor
Modified: 2010-10-04 14:56 UTC (History)
6 users (show)

See Also:

Attachments

Description contributor 2010-05-18 08:01:52 UTC 
Section: http://www.whatwg.org/specs/web-apps/current-work/#offsets-into-the-media-resource

Comment:
"It might not be zero if the clip's timeline is not zero-based" - please make
startTime start at 0 even for clips that are not zero-based, to make the API
simpler to use for authors. If this change is made, startTime seems to be
equivalent to buffered.start(0). Maybe we should remove startTime altogether?

Posted from: 85.227.153.170
Comment 1 Simon Pieters 2010-05-18 08:05:25 UTC 
s/buffered/seekable/
Comment 2 Philip Jägenstedt 2010-05-18 09:12:19 UTC 
I agree, I didn't support adding startTime, although I wasn't fighting it very hard either. Opera always returns 0 is eager to drop support for the property altogether. The use case (server-side media fragments) isn't important enough in my opinion. I imagine it's also a pain to get this information out of the media framework, which is why I haven't even tried.
Comment 3 Ian 'Hixie' Hickson 2010-08-25 22:39:25 UTC 
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Accepted
Change Description: no spec change
Rationale: This seems to have been fixed already.