" * Each person will be able to decide whether to activate the DRM implementation or to leave it off and not watch DRM-controlled content.
* We have surrounded the closed-source portion with an open-source wrapper. This allows us to monitor and better understand the scope of activities of the closed-source code."
So your hypothetical built-into-the-browser and on-by-default implementation does not describe the same thing that has been announced for Firefox. Indeed the actual plan is quite close to what you suggest in your final paragraph.
" * Each person will be able to decide whether to activate the DRM implementation or to leave it off and not watch DRM-controlled content.
* We have surrounded the closed-source portion with an open-source wrapper. This allows us to monitor and better understand the scope of activities of the closed-source code."
So your hypothetical built-into-the-browser and on-by-default implementation does not describe the same thing that has been announced for Firefox. Indeed the actual plan is quite close to what you suggest in your final paragraph.
[1] https://blog.mozilla.org/blog/2014/05/14/drm-and-the-challen...