Do more on the web, with a fast and secure browser!
Download Opera browser with:
Opened two issues related to mv3:
Request to allow webRequestBlocking usage in mv3: https://forums.opera.com/topic/88926/browser-support-webrequestblocking-in-mv3
Request to permit webRequestBlocking permission in the add-on linter for mv3 extensions: https://forums.opera.com/topic/88925/store-linter-allow-passing-webrequestblocking-permission-in-mv3
Currently the store linter rejects extensions with webloc files. These files can be useful for drag-and-drop icons and do not seem to give any security risks.
This has previously been reported as DNA-123933
Currently when passing a i18n variable to short_name, like this:
__MSG_extension_short_name __
The add-on linter rejects the extension. It should not restrict it as much as it does now. The current limit is 12 characters, while other stores use a limit of 45. It could at least opt a limit of at least 32 characters.
Currently the linter disallows uploading mv2 extensions with the scripting permission. This is in stark contrast with other stores which do not restrict the scripting permission.
Can Opera allow extensions to use the webRequestBlocking API in mv3? There is high demand for this see:
https://www.reddit.com/r/operabrowser/comments/1u1o5eb/comment/oqzuwsf/
Currently when attempting to upload an mv3 extension with webRequestBlocking in permissions or optional_permissions, Opera Add-ons refuses to accept this.
This is in stark contrast with the Chrome Web Store which allows to submit mv3 extensions with the webRequestBlocking permission.
It is then up to the browser whether or not to respect the webRequestBlocking permission and allow extensions to use it or not.
@osmantseng Thanks for reporting this! I was not able to reproduce your issue.
What custom shortcut were you trying to add? Does the issue happen for any custom shortcut you try to add or only some?
When does the issue appear? When opening the dialog or only on the final step of actually adding the custom shortcut?
Screenshot would be helpful!
@Katsygin there is no harm in using extensions with manifest v2. Once Opera announces deprecation of manifest v2, many extensions like probably Bitwarden will update the extension they serve on the Opera add-on store to be manifest v3 supported. Many developers hold back tho for compatibility reasons and for some features which are only available in manifest v2.
@Katsygin the 4.9.2 version from AdBlock Plus as listed on the Opera add-ons store is using manifest v2. They might have a manifest v3 version ready when Opera makes the switch, that does not change the fact they currently serve a manifest v2 version on the Opera add-ons store. Trust me, I checked the running extension myself.
@leocg Yes, still would be nice if Opera would hide these warnings for the time being until they have an mv3 schedule.
@Katsygin Both bitwarden and Adblock Plus might use mv3 on the Chrome Web Store. On the Opera Store however, both of them are using mv2.
@Katsygin What version are you talking about? Seems the bitwarden extension provided to Opera is still using mv2.
@Katsygin See: https://forums.opera.com/topic/50569/manifest-v3-opera/20
Seems Opera forgot to inform developers about their mv3 timeline.
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?
@Katsygin Thanks for sharing! Don't worry, G App Launcher will continue to work on Opera.
@Katsygin Hi! Thanks for letting us know! Can you share a screenshot of what the message looks like?
@gmiazga Thanks for the MV3 timeline!
Is it already clear how Opera will handle browser-specific choices and features?
Mozilla Firefox decided to handle MV3 a bit different than Chrome to help developers and users:
(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?
@wendyallison Hi Wendy, can you share a screenshot of both the options page and the page you are trying to share + dropdown?
@wendyallison Add it in the options page, and click on "Share page on Facebook". Let me know if you got it to work. Just in case, I've updated the extension to v5.7, with additional improvements and changes.