Request for Mozilla Position on an Emerging Web Specification Specification Title: Web Environment Integrity API Specification or proposal URL (if available): https://rupertbenwiser.github.io/Web-E...
But that’s exactly the point. The fact that they have given up before on something as small (compared to this proposal that could affect a lot more content) as video/audio DRM only means that anything they say about this is meaningless. Google already knows that Firefox fill just give in and implement it anyway, so they have literally no reason to listen to them.
But I understand that there’s nothing they could’ve done about it, given their market share. Just like they can’t do anything in this situation, apart from “strongly disagreeing” before eventually being forced to implement it anyway, because without it more and more websites will stop working at all, and it will be necessary to keep users.
But that’s exactly the point. The fact that they have given up before on something as small (compared to this proposal that could affect a lot more content) as video/audio DRM only means that anything they say about this is meaningless. Google already knows that Firefox fill just give in and implement it anyway, so they have literally no reason to listen to them.
But I understand that there’s nothing they could’ve done about it, given their market share. Just like they can’t do anything in this situation, apart from “strongly disagreeing” before eventually being forced to implement it anyway, because without it more and more websites will stop working at all, and it will be necessary to keep users.