-
## Context
This ticket is to ensure that all of our mv3 e2e tests run, and pass, on firefox, once we start creating mv3 builds for firefox
## Approach
After [17901](https://app.zenhub.com/workspac…
danjm updated
8 months ago
-
### Describe the bug
This support should piggyback off the support we have for dapp pages. It might already be supported with the dapp work found in the related epics.
### Steps to reproduce
…
-
Currently it is required to load all controllers for extension UI to be painted. To make things more performant in MV3 we plan to implement asynchronous loading of controllers. Initial version of UI w…
jpuri updated
9 months ago
-
The PR in question #46658
Claims to address #18407 #21721 and #35837
But what it does, it adds `materialized_views_ignore_errors` setting to INSERT.
The original questions were: how we prevent a …
-
In Chrome: If you click an extension icon on a tab on which you have not granted host permissions, it requires that you refresh the page before it will load the extension. You can reload the page as m…
-
https://developer.chrome.com/docs/extensions/mv3/intro/mv3-migration/
-
Are there plans to migrate the extension to manifest v3 this year?
-
migrate exxtension to manifest v3
https://developer.chrome.com/docs/extensions/mv3/intro/mv3-overview/
-
Google Chrome
uBlock Origin Lite 2024.6.17.766
Does this rule not work due to MV3 limitations?
`*$removeparam=xtor` ~> **AdGuard URL Tracking Protection**
```
https://www.bbc.com/ukrainian/…
-
### What happened?
After updating from 83 to 84, the build process errors out due to:
``` shell
🔴 ERROR | Failed to resolve './gen-assets/icon16.plasmo.png' from './.plasmo/chrome-mv3.plasmo.man…