> From CSS to AACS to HDCP[1]. I was hoping Firefox (and perhaps Chromium, but Google would probably not be so kind as to open source that part of the code) would have the DRM code built in so that we can spoof the whole thing with simple modifications.
That fails to fulfil the requirements of pretty much any level of DRM, and hence such an implementation would be totally ignored and unused, and sites would continue to use Flash in preference to it.
(I wish I could find the document Google published last year about the different levels of DRM the industry has been concluded need to exist for them to use; alas, I cannot!)
Primarily to have a standard API to determine what DRM schemes the UA supports. A less important part of it is to avoid a different code-path for each different DRM scheme each with its own API.
That fails to fulfil the requirements of pretty much any level of DRM, and hence such an implementation would be totally ignored and unused, and sites would continue to use Flash in preference to it.
(I wish I could find the document Google published last year about the different levels of DRM the industry has been concluded need to exist for them to use; alas, I cannot!)