This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Back to bug 8278

Who When What Removed Added
ian 2010-01-05 08:01:33 UTC Status NEW RESOLVED
Resolution --- LATER
ian 2010-05-06 08:54:55 UTC Assignee dave.null ian
mike 2010-10-04 14:57:35 UTC CC public-html-wg-issue-tracking
Component HTML5 spec (editor: Ian Hickson) pre-LC1 HTML5 spec (editor: Ian Hickson)
ian 2012-09-25 05:04:02 UTC Component pre-LC1 HTML5 spec (editor: Ian Hickson) HTML
Product HTML WG WHATWG
Target Milestone LC ---
ian 2013-01-05 01:47:32 UTC Status RESOLVED REOPENED
Resolution LATER ---
robin 2013-01-14 16:03:51 UTC CC robin
public-rdfa-wg 2013-01-24 06:32:05 UTC URL http://www.whatwg.org/specs/web-apps/current-work/#dom-media-currenttime https://www.w3.org/Bugs/Public/show_bug.cgi?id=19061
CC public-rdfa-wg
mike 2013-01-24 07:12:10 UTC CC public-rdfa-wg
ian 2013-03-19 17:36:55 UTC Status REOPENED NEW
Target Milestone Unsorted Needs Impl Interest
ian 2013-07-15 23:16:55 UTC Summary why can't the frame number be requested? It's video, position is expressed in frames, not in seconds. a frames per second value could easily convert this to seconds <video> why can't the frame number be requested? It's video, position is expressed in frames, not in seconds. a frames per second value could easily convert this to seconds
Severity normal enhancement
ian 2013-10-14 19:42:35 UTC Blocks 23493
ian 2013-10-14 21:31:21 UTC Summary <video> why can't the frame number be requested? It's video, position is expressed in frames, not in seconds. a frames per second value could easily convert this to seconds <video>: video.currentTime variant that returns a frame number
philipj 2013-10-16 11:26:16 UTC CC philipj
hoangminh120814 2016-07-20 22:57:08 UTC OS other All
QA Contact public-html-bugzilla contributor
slave.loren 2017-01-19 11:28:59 UTC CC slave.loren
annevk 2017-07-21 10:30:44 UTC Status NEW RESOLVED
CC annevk
Resolution --- WONTFIX

Back to bug 8278