[Webkit-unassigned] [Bug 52697] Frame accurate seeking isn't always accurate

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=52697





--- Comment #4 from Jer Noble <jer.noble at apple.com>  2011-01-19 13:57:30 PST ---
Unfortunately, seeking directly to a frame boundary will always be problematic in floating-point math.  Chromium solved this problem by effectively shifting the start time of every frame earlier by 1/2 the previous frame's duration.  This means Chromium will always be off by 1/2 a frame.  You can verify this in the Chromium nightlies, and loading the testcase URL, and setting the video's time to 0.51.  It will seek to the frame containing 00:13, even though it's well within the 00:12 frame's duration.

I don't recommend we fix this bug in the same way as chromium.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.