Browsers can't play m3u8's natively in the first place, client-side JS is responsible for piping the fragments into the video element. As sibling comments point

Browsers can't play m3u8's natively in the first place, client-side JS is responsible for piping the fragments into the video element. As sibling comments point out, I think it's more a case of "can't be bothered", than "can't".