Chrome >= 142 has issues with HLS seeking

A similar followup to the last issue I submitted.

Try loading these in Chrome:

MediaElements Player: https://seventhcycle.net/bugs/mejs_hls/?native=0

Native Video Player: https://seventhcycle.net/bugs/mejs_hls/?native=1

And looking at the development tools / networking tab.

If you try jumping around in the video (seeking) in the native player, Chrome will intelligently seek to the .ts file within the m3u8 manifest where the video is supposed to load.

HOWEVER:

The MediaElements player does not. In this case, much of the time the mediaelements player will sequentially try loading .ts files up until the point in the movie corresponding to the ts file. In the case of a slow connection, it's loading hundreds of megabytes of files that aren't going to be rendered on screen to the viewer, and takes a longer amount of time for the movie to play again.

I imagine now that Chrome is using HLS internally that there's some sort of loading mechanism in the player that needs to be disabled in new builds. I just haven't been able to track down where in the player code that's happening.

Any help on this would be greatly appreciated. Please let me know if anything is unclear. Thanks!