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.
Just goes to show, google is an ad company first and foremost and they’re in the process of cutting out any competition to their dominance.
Props too to Vivaldi for blowing the whistle as they have access to all the upcoming chromium builds being a fork.
They didn’t blow any whistles, the proposal was public and lots of people spoke out against it already.
Besides, I like Vivaldi, but they’re part of the problem.
The only reason this discussion is happening is because everyone and their grandma decided it’s a great idea to re-skin a browser built by an ad-company and expect them not to abuse their position.
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.
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?