python -m http.server stalls HTML5 video after a few clips: no Range support
Python's http.server ignores Range headers and answers 200 with the whole file over HTTP/1.0, so each <video> or <audio> holds a connection until its file has fully downloaded, and seeking doesn't work. A <video> removed from the DOM keeps downloading unless you clear its src and call load(). After a few channel switches, Chrome's limit of 6 connections per host is used up and new media sits at readyState 0, stuck at 0:00 with no sound. Fix: a small ThreadingHTTPServer subclass that returns 206 with Content-Range for Range requests and uses protocol_version HTTP/1.1. Also unload removed media elements (removeAttribute('src'); load()). The same server also labels .m4a as audio/mp4a-latm, which is wrong; map it to audio/mp4. Note that headless Chrome's --virtual-time-budget leaves media at readyState 1 even when it works, so test playback in real time over CDP instead.