Also, the plugin is a users choice to install. The DRM in the HTML5 specs would be deeply incorporated inside the navigators codebase. It should be a choice, no

Also, the plugin is a users choice to install. The DRM in the HTML5 specs would be deeply incorporated inside the navigators codebase. It should be a choice, not an obligation. If you are like me, and try to keep the proprietary stuff to a minimum on some of my laptops, then I would not use this version of FF/Chrome. I would have to use a forked version without the DRM specs (which i think would be a way of sticking it to the W3C).