Which is why we're hoping to get a response from someone on or familiar with the development team, I believe.

Not really. They CAN (and do) modify the Chromium code each time an update comes out. Vivaldi makes underlying changes each release as it makes new code work with their features. Brave has already stated that these proposed changes will not affect their manipulation of the code or how their built-in ad blocking feature works. Chrome tacks on Google-specific features to the Chromium code, and I'm sure that Opera does the same.

Chromium itself is designed to be modified by end users to add or remove features in their software.

The question was whether or not changes to Chromium's base code would impact extensions. This is listed on the extensions page. I believe it's a fair question whether or not Opera's built-in adblocker will be impacted by proposed changes to Manifest V3.

@sgunhouse It is listed on the Extensions page of Opera. I believe that's part of my initial confusion.

I'm curious about this as well. Right now, I know that Brave's internal adblock is safe, but I really like Opera's adblocker on mobile devices. It'd be a shame to lose that as an option.

I get the following error when I try to log into sync.opera.com/web

AccountsAPIError: oauth2 server error (500)

@slytheringirl I appreciate the suggestion! I hope I didn't sound ungrateful.

@slytheringirl First time, I got an API error, then I got a 403 error.

If I'd have known I'd have lost functionality like this, I wouldn't have done it.

Is there going to be a workaround for this? I'd hate to think that by using a built-in security feature that I'd lose a feature that I really liked about Opera.