Reduced time precision in media currentTime
Categories
(Core :: Audio/Video: Playback, defect)
Tracking
()
People
(Reporter: ble-m, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/115.0
Steps to reproduce:
- Visit https://gh.ltgc.cc/octavia/test/fakeQy.htm (as an example).
- Execute
self.debugTimeSource = true;
in the console to get the player emit timestamps. - Play any of the listed demos, and see the time value emitting in the console.
Actual results:
Value of the currentTime
property gets increased in a 40 millisecond step with random jitters, instead of the 2-millisecond precision when privacy.reduceTimerPrecision
is enabled. This weird stepping doesn't go away when privacy.reduceTimerPrecision
is disabled.
Expected results:
Value of currentTime
should've been increased smoothly, like on Chromium browsers.
Reporter | ||
Comment 1•9 months ago
|
||
The bug was spotted on 126.0b6 (Dev Edition), and confirmed to exist from 115.10.0 (ESR), all the way to 127.0b1 (Nightly Build available at the time of the report).
Comment 2•8 months ago
|
||
Managed to reproduce this issue on:
- Firefox Nightly 128.0a1;
- Firefox Beta 127.0b1;
- Firefox 126.0;
Tested and reproduced on:
- Windows 10;
- macOS 12;
- Ubuntu 22;
Setting to Product to ‘DevTools’ and the Component to ‘Console’ . Please change if there’s a better fit, thank you.
Setting as NEW so the developing team can have a look.
Comment 3•8 months ago
|
||
Console is only used to diagnose the issue. Moving to more appropriate module so the right folks can have a look
Reporter | ||
Comment 5•7 months ago
|
||
(In reply to Jim Mathies [:jimm] from comment #4)
Does this reproduce in Chrome?
No, at least not in the abysmal time interval Firefox currently has.
Updated•2 months ago
|
Description
•