169
Unpacking Google’s new “dangerous” Web-Environment-Integrity specification (vivaldi.com)
submitted 11 months 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
[-] Qualanqui@lemmy.nz 8 points 11 months ago

I agree with you, I'd love to live in the world where Vivaldi chose Gecko instead of Chromium, but we've only got the cards we've been dealt so at least the Vivaldi team are always very vocal about this and have always said they're going to work around Google's more draconian decisions.

[-] Trarmp@feddit.nl 4 points 11 months ago

I just want WebKit for windows :(

It has a bunch of fine browsers on Linux, why isn’t there a decent GTK port for windows?

this post was submitted on 25 Jul 2023
169 points (97.7% liked)

Programming

16210 readers
43 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

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