Issue Report - Netflix Seek Inaccurate
Hey, There's an issue with Netflix's seek function where it never jumps to the exact timestamp. Instead, it's always off by a few hundred milliseconds to a few seconds. This happens both when using Netflix's `±10s` buttons and when calling their seek API. The issue is most consistent on Edge (happens 100% of the time), but some Chrome users (especially on macOS) have reported it too. Other video platforms don't seem to have this problem, so it looks like something specific to Netflix+Edge combo. **Steps to Reproduce:** - Open Netflix in Edge - Play any video - Try seeking with the built-in `±10s` buttons - Notice that it never lands exactly where it should. **Why This Matters:** We're building an extension that helps users navigate subtitles smoothly and record them, so accurate seeking is a big deal for us. This issue makes things frustrating for our users, especially when trying to jump to a specific subtitle. Would love to know if this is something related to how Edge handle video playback.Latest Windows Insider 19654.1 and Edge releases with Netflix
Hey all, My Dev PC has just upgraded Windows Fast Ring to 19645.1. Since this upgrade neither current Edge Dev Version 85.0.538.0 (Official build) dev (64-bit) or Edge Stable Version 83.0.478.45 (Official build) (64-bit) will stream any Netflix programs. On my Windows stable PC, both these versions of Edge work fine with Netflix. On the Fast Ring PC, Firefox works fine with Netflix. Has anyone experienced this behaviour?
