Matt May

@OliverWang13 and I have begun to put together a to-do list specifically catered to migrating Optmeowt to MV3. Here is what we have so far: - Update manifest.json manifest_version key...

@OliverWang13, I was able to replicate these results, and once I enabled host permissions the header signal was sent as it should. One potential workaround for requesting permissions manually for...

Note to update readme/Wiki and tutorials accordingly based on new permission requests after MV3 migration.

So far I have implemented a button to the OptMeowt popup, allowing for a more programatic way to enable host permissions. Once these permissions are set, they will persist on...

@OliverWang13 and I met today and implemented a popup in the options page upon installation prompting the user to enable host permissions using a button that then sets these permissions....

We have implemented DOM Signal functionality into our MV3 migration and have removed a large majority of the browser checks from the codebase. In the reference server, the DOM signal...

@OliverWang13 and I have met and solved the problem resulting in bugs with the Website Response and extension icon. These bugs occurred because of the argument `sender.origin` was marked as...

Here is a checklist @OliverWang13 and I put together to go through after implementing MV3 changes: - [ ] - 3rd Party Domains button responding correctly - [ ] -...

For @OliverWang13: - [ ] - 3rd Party Domains button responding correctly - [ ] - Website Response button in popup reflects GPC Signal information - [ ] - Domain...

@OliverWang13 and I have implemented a new storage system using IndexDB to store 3rd Party Domain data to work around the deprecation of persistent background pages in MV3. This has...