If yes, what's the difference which allows Chrome to work with DRM and doesn't allow another code to do that?
I don't think I understand the problem. What does it mean "won't allow DRM" - you can always write code which you like, right?
If yes, what's the difference which allows Chrome to work with DRM and doesn't allow another code to do that?
I don't think I understand the problem. What does it mean "won't allow DRM" - you can always write code which you like, right?
https://wiki.archlinux.org/index.php/chromium#Widevine_Conte...
The author can't get a license.
(Firefox is not a chromium derivative.)
I mean, if something open source works, anything else open source can also be made to work.
Even if something that works includes binary blobs, you can still modify open source parts while keeping that blob and keeping the system working. So I'm not sure what is the original problem.
Chrome browser (which is based on Chromium, plus various Google proprietary features on top of it) is not.