[Webkit-unassigned] [Bug 52697] Frame accurate seeking isn't always accurate
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Wed Jan 19 17:46:15 PST 2011
https://bugs.webkit.org/show_bug.cgi?id=52697
--- Comment #10 from Rob Coenen <coenen.rob at gmail.com> 2011-01-19 17:46:15 PST ---
I have build Webkit with the patch and it now correctly displays frame 00:00:00:13.
But after some testing I got the timecode at 00:00:20:13 burned in, but calculated = 00:00:20:14
video.currentTime = 20.559600830078125 at this point
when set in Chromium video.currentTime to 20.559600830078125 it correctly seeks to 00:00:20:14
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the webkit-unassigned
mailing list