Unpacking Google’s new “dangerous” Web-Environment-Integrity specification
![](https://programming.dev/pictrs/image/104fdd2c-9db4-4643-bf4c-4b2c28750dc3.png)
![](https://programming.dev/pictrs/image/8140dda6-9512-4297-ac17-d303638c90a6.png)
![Unpacking Google’s new “dangerous” Web-Environment-Integrity specification](https://forkk.me/pictrs/image/5e699abf-0c5a-4e52-9c87-12f87aba60a9.jpeg?format=jpg&thumbnail=256)
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
Don’t not be evil