Standards control has been never always direct since JScript days, the dominant players do what they please, and by the nature of dominance web app developers h

Standards control has been never always direct since JScript days, the dominant players do what they please, and by the nature of dominance web app developers have to comply follow their tools, and standards get established de-facto. Specifically, moves like changes in manifest V3 and removal of chrome.webRequest is aimed squarely at adblocking, Forcing DRM in HTML5 is a step in this direction as well and can become dangerous in conjunction with AV1 enhancements . For example it may become feasible to dynamically mux content and ad streams without a separate network request if encoding is not as expensive as H264 today with AV1 . Coupled with DRM on HTMl5 it would be impossible for any plugin as streams will never be exposed available for "Piracy reasons". Even HDMI has support for DRM , the only analog/open/accessible format left will be the light stream to your eyes.