Manifest v3 Opera

[gmiazga]

gmiazga Opera @carlosjeurissen last edited by

What can we expect from Opera in terms of Manifest v3?
When and will Opera support Manifest v3? If so, in what form?

Manifest 3 is already supported in Opera in the same form as Chrome supports it.

Will the webRequest API still be supported in v3 like Firefox decided to do?
When can expect manifest v2 to nolonger be available?

We are aware that the change introduced by Chrome is not welcomed by some extension developers. On the other side, we know that the problem with extensions using the API to harm users is really big and severe. It's is a tradeoff - should we better safety of users or keep the API flexible? It's similar to the situation when CORS was introduced and XHR cross-origin requests stopped to work - many malicious scripts started to be useless but aside scripts intended to improve productivity got afflicted.
For the time being we observe how the new declarativeNetRequest API is adopted by developers - we don't rush here. Like Chrome we don't support webRequest API in v3 but we still support it in v2 (also in Opera addons portal) and we don't have strict dates to remove it.

[carlosjeurissen]

carlosjeurissen last edited by

Thanks so much for the extensive reply Gmiazga!

Does this mean the Opera addons portal already accepts extensions with manifest v3?

Currently wondering if the chromium source would allow easy enabling of the webRequest API for manifest v3 so Opera could decide to keep it.

Lastly, is there an end-of-life date / timeline defined for manifest v2?

[qpayct]

qpayct @gmiazga last edited by

@gmiazga said in Manifest v3 Opera:

Manifest 3 is already supported in Opera in the same form as Chrome supports it.

Is there a tutorial how to migrate from v2 to v3 on Opera?

Because my extension works on Google and Edge, but refuse to work with Opera.

The error I get says that "content_security_policy" value must be string when in fact in Google's manifest v3 its an object.

[carlosjeurissen]

carlosjeurissen @qpayct last edited by

@qpayct Can confirm your issue about the CSP. When you remove it Opera states "Manifest format version is not supported.".

@gmiazga @qpayct @namero999 Currently the Opera Add-ons Store doesn't support manifest v3 extension packages. When can we expect the store to support them?

@gmiazga Thanks a lot for the explanations. Is there any reason why the non-blocking webRequest API and/or blocking webRequest API won't be supported in v3 by Opera?

[xantares]

xantares @gmiazga last edited by

@gmiazga

Opera's addons.opera.com doesn't seem to accept M3 extension updates, though.

I get the feeling, Opera is kind of slightly abandoning its own extension repository, by the way. Is it right, that users as well as developers should concentrate on Chrome's addon store instead?

[nfl0]

nfl0 last edited by

when M3?

[carlosjeurissen]

carlosjeurissen last edited by

@gmiazga By now we as developers and users really need to know when Opera will support Manifest v3 on the Opera Store. OR, if the Opera Store will be phased out and we need to migrate people to the Chrome Web Store.

[gmiazga]

gmiazga Opera @carlosjeurissen last edited by

@carlosjeurissen at the moment we do not have plans for closing our store. Will try to get some information about plans for allowing v3 in our store.

[gmiazga]

gmiazga Opera @carlosjeurissen last edited by

@carlosjeurissen I got information that support for v3 in addons.opera.com has been scheduled for development. No ETA on it yet, so I will try to get this post update.

[nfl0]

nfl0 @gmiazga last edited by

@gmiazga wen

[vjik7]

vjik7 @gmiazga last edited by

@gmiazga Is there ETA already?

[gmiazga]

gmiazga Opera @vjik7 last edited by

@vjik7 I got information that upload od manifest v3 extensions should be possible within a week. Migration of old extensions and deprecation of v2 will be done as separate tasks later.

[vjik7]

vjik7 @gmiazga last edited by

@gmiazga Any news?

[gmiazga]

gmiazga Opera last edited by

It took way longer than expected but it's finally here. Changes have been deployed on production and it should be possible to upload extensions using manifest v3.

[carlosjeurissen]

carlosjeurissen @gmiazga last edited by

@gmiazga Thanks for the MV3 timeline!

Is it already clear how Opera will handle browser-specific choices and features?

• How will the sidebar API change in MV3? (See https://github.com/w3c/webextensions/issues/128)

Mozilla Firefox decided to handle MV3 a bit different than Chrome to help developers and users:

• Will the webRequest still be available in MV3 (Unlike in Google Chrome)
• Will Opera keep supporting non-persistent background scripts?

(When) does opera want to stop supporting MV2 extensions on the store and in the browser? Due to all the issues with MV3, can we as developers ask for extended support of MV2 on the Opera Store? Or allow publishing both MV2 and MV3 at the same time for best backward compatibility?

[alitoolsio]

alitoolsio last edited by

@gmiazga when is the full transition to Manifest V3 planned, and when will it be prohibited to load the extension with Manifest V2?

Or is there no certainty yet about when exactly this will happen, and it is safe to continue loading the extension with Manifest V2?

[Halterka]

Halterka @alitoolsio last edited by

@alitoolsio I noticed that few developers like SIMKL's Netflix Enhancer have already started updating their browser extension to Manifest V3.

I still kinda use those old browser extension that run on Manifest v2 (which were not updated for ages) but still useful to me - I wonder, what will happen to those apps.

[carlosjeurissen]

carlosjeurissen last edited by

People are reporting mv3 warnings in the extensions panel.

https://forums.opera.com/topic/36230/app-launcher-customizer-for-google/32

Why is this appearing before Opera gave any statement on their mv3 schedule? What is the timeline?

[leocg]

leocg Moderator Volunteer @carlosjeurissen last edited by

@carlosjeurissen Probably is Chromium doing it.

[carlosjeurissen]

carlosjeurissen @leocg last edited by

@leocg Yes, still would be nice if Opera would hide these warnings for the time being until they have an mv3 schedule.