170

Unpacking Google’s new “dangerous” Web-Environment-Integrity specification (vivaldi.com)

submitted 1 year ago by ruffsl@programming.dev to c/programming@programming.dev

12 comments fedilink hide all child comments

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's thread
view the rest of the comments

[-] ruffsl@programming.dev 19 points 1 year ago

Is Web Environment Integrity a risk to the accessibility of the Internet?
- https://programming.dev/post/831937
Google’s nightmare “Web Integrity API” wants a DRM gatekeeper for the web
- https://programming.dev/post/916235
Mozilla opposes Web Integrity API proposal
- https://programming.dev/post/929260

this post was submitted on 25 Jul 2023

170 points (97.8% liked)

Programming

17314 readers

23 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 1 year ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz