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.