Well, for one example, Google basically shut off audio for the entire web a while back and panicked and reverted it once people angrily pointed out they had mes

Well, for one example, Google basically shut off audio for the entire web a while back and panicked and reverted it once people angrily pointed out they had messed up. Given their willingness to destroy swathes of old content (just like killing - for good reason, at least - all existing Flash and Unity content permanently) it's not hard to imagine them disabling HTTP permanently in Chrome, with exceptions for enterprise LTS builds if you have group policies. Typically Google justifies these decisions to kill portions of the web with "security" and/or "user experience", and it's easy to use both of those reasons to justify disabling HTTP forever. You can remove the 'secure' indicator!