Frame accurate seeking of 120 FPS video does not work

Issue #618335 • Assigned to Brian K.


Jul 14, 2014
This issue is public.
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce


Repro Steps:

  1. goto

1.hit next button and time should update

currentTime will not be updated.

Expected Results:

The videoElement should seek to the next frame.

Actual Results:

Dev Channel specific:



0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Venkat K.”

      Changed Assigned To from “Venkat K.” to “IE F.”

      Changed Status to “Won’t fix”

      Changed Assigned To from “IE F.” to “Steve B.”

      Changed Status from “Won’t fix”

      Changed Assigned To from “Steve B.” to “IE F.”

      Changed Status to “Won’t fix”

      Changed Assigned To to “Jerry S.”

      Changed Status from “Won’t fix”

      Changed Assigned To to “Sudhakar P.”

      Changed Assigned To from “Sudhakar P.” to “Brian K.”

    • Works in Chrome – it steps forward/backwards by 0.0083333

      With CES 2018 and the explosion of 120fps HFR, this will be important to fix compliance on this.

      That said, EDGE properly plays back embedded 120fps HFR videos in realtime on 120Hz and 240Hz displays, so that part is working fine.

    • However, single-stepping 120fps fails to work properly in Edge 16.16299 (whether on 60Hz display or 120Hz+ display). Confirmed.

    • Possible related issue:

      Internal Edge framerate limiter of 105 (or some 1.75 multiplier factor on 60 Hz) might be interfering with this capability. That other bug may potentially need to be fixed first.

    You need to sign in to your Microsoft account to add a comment.

    Sign in