Google Chrome 96 Breaks Twitter, Discord, Video Rendering and More (bleepingcomputer.com) 19
Google Chrome 96 was released yesterday, and users are reporting problems with Twitter, Discord, and Instagram caused by the new version. BleepingComputer reports: The issues have been reported to Google in a Chromium bug post where Google employees have started to investigate the problems. "We're continuing to see user reports about this behavior, including reports from our social team," notes Google product manager Craig Tumblison. "One user has shared that disabling the "chrome://flags/#cross-origin-embedder-policy-credentialless" flag resolves the behavior. Another report shares a specific error message: "The connection was rejected at https://cards-frame.twitter.com". Test team, would you be able to try enabling that flag to see if the behavior appears?"
The 'chrome://flags/#cross-origin-embedder-policy-credentialles' flag is related to a new Cross-Origin-Embedder-Policy feature released with Chrome 96. Google states that you can fix these bugs in some cases by setting the "chrome://flags/#cross-origin-embedder-policy-credentialless" to disabled. If you are affected by these issues, you can copy and paste the above chrome:// address into the Google Chrome address bar and press enter. When the experimental flag appears, please set it to Disabled and relaunch the browser when prompted.
The 'chrome://flags/#cross-origin-embedder-policy-credentialles' flag is related to a new Cross-Origin-Embedder-Policy feature released with Chrome 96. Google states that you can fix these bugs in some cases by setting the "chrome://flags/#cross-origin-embedder-policy-credentialless" to disabled. If you are affected by these issues, you can copy and paste the above chrome:// address into the Google Chrome address bar and press enter. When the experimental flag appears, please set it to Disabled and relaunch the browser when prompted.
"Problems" (Score:5, Funny)
"We're continuing to see user reports about this behavior, including reports from our social team," notes Google product manager Craig Tumblison.
Translation: We're noticing that users are detected our attempts to further break the web to steer them into our walled ecosystem, which appears to be failing.
Re: (Score:3)
Re: (Score:2)
Looking into the problem it seems that Google is adding an important security enhancement that prevents unintended tracking across sites (including their own). So if a random site adds a Google widget or a 3rd party ad or something it doesn't get access to the main site's credentials unless explicitly opted in by the developer.
The opt in is needed for some sites functionality.
Re: (Score:2)
"We're continuing to see user reports about this behavior, including reports from our social team," notes Google product manager Craig Tumblison.
Translation: We're noticing that users are detected our attempts to further break the web to steer them into our walled ecosystem, which appears to be failing.
Indeed. There is no way they did not know that before. Even Google does not test its products this shoddily.
That settles it... (Score:3)
I'm upgrading immediately!
Re: (Score:2)
yeah, I'm trying to see the downside of this, and not succeeding.
These all seem to be features.
General system stability improvements (Score:2)
to enhance the user's experience.
We're not all as diligent as Nintendo.
Slashvertisement? (Score:2)
Chrome 96 Breaks Twitter,
Upgrade immediately!
Discord,
*tsk*....eh, I use the desktop app
Video Rendering and More
Dammit, now I'm conflicted!
Who are the credentialles? (Score:2)
Are the credentialles like the federales, except responsible for credentials?
(Yes, I know, what editors?)
corporate IT issues (Score:3)
make the chrome flags option not a good solution. When the http images in https pages issue came along, lots of customers came back and said they aren't allowed to change their chrome flags settings due to security policies from their company.
Re: (Score:3)
If you're using discord on your company PC you have more serious issues. But jokes aside Chrome flags are still a good option, precisely because they can be controlled via security policy. Something is broken, talk to your IT department who rolled out a Chrome update without testing it.
Automatic updates considered harmful (Score:3)
Re: (Score:2)
Re: (Score:2)
like while I'm in the middle of doing something important that shouldn't be interrupted
Given how updates to Chrome apply silently in the background you've either done something very wrong, or are doing something *VERY* important.
You can control your upgrade schedule if you want, but I take big issue with you calling them "harmful". We have 25 years of experience showing that relying on users to apply updates themselves is a fucking security nightmare, and one of the best advances we have made in IT security over the years is to remove the user's manual intervention.
SiteGround (Score:2)
Re: (Score:2)
STOP (Score:4, Informative)
Don't they have anything better to do? Stop developing Chrome. It's ready. It's been ready five years ago.
Re: (Score:2)
It's ready. It's been ready five years ago.
What's ready? Just as a simple experiment download a 5 year old version of Chrome and try and run Office 365. You'll see how unready it actually is.
Re: (Score:2)
The problem is adding flaming hoops for "security" that don't even actually improve security. Add in a w3c that has abandoned it's reason to be and yet continues to exist.