Unpacking Google’s new “dangerous” Web-Environment-Integrity specification
vivaldi.com
Will accessibility tools that rely on automating input to the browser cause it to become untrusted? Will it affect extensions? The spec does currently specify a carveout for browser modifications and extensions, but those can make automating interactions with a website trivial. So, either the spec is useless or restrictions will eventually be applied there too.
You are viewing a single comment
Even if you were to diminish any valid reasons to not add this DRM feature, what are the actual reasons they think are pro consumer?
Harder for scammers/hackers iirc.
But this also makes it harder for devs to run tests.
How do you figure?
Saw some Google bootlicker on GitHub issues talking about how the policy will prevent a lot of automated stuff including bots and many hacker tools.