9760 2010-05-18 08:01:52 +0000 "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 2010-10-04 14:56:10 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified Other other RESOLVED WORKSFORME http://www.whatwg.org/specs/web-apps/current-work/#offsets-into-the-media-resource P3 normal --- 1 contributor ian ian mike philipj public-html-admin public-html-wg-issue-tracking zcorpan public-html-bugzilla oldest_to_newest 35741 0 contributor 2010-05-18 08:01:52 +0000 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 35742 1 zcorpan 2010-05-18 08:05:25 +0000 s/buffered/seekable/ 35745 2 philipj 2010-05-18 09:12:19 +0000 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. 37862 3 ian 2010-08-25 22:39:25 +0000 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.