- From: <bugzilla@jessica.w3.org>
- Date: Tue, 03 Dec 2013 22:32:32 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23169
Jerry Smith <jdsmith@microsoft.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|FIXED |---
--- Comment #17 from Jerry Smith <jdsmith@microsoft.com> ---
Microsoft recommends that the frame delay metrics be double-precision with
units in seconds to match other timing variables used for media. This matches
our implementation in IE11.
Doing this would require the following tweak to Displayed Frame Delay:
The delay between a frame's presentation time and the actual time it was
displayed, in a double-precision value in seconds & rounded to the nearest
display refresh interval. This delay is always greater than or equal to zero
since frames must never be displayed before their presentation time. Non-zero
delays are a sign of playback jitter and possible loss of A/V sync.
totalFrameDelay would similarly be double-precision in seconds as a summation
of the individual frame delays.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 3 December 2013 22:32:34 UTC