Migrate to Manifest V3

[aybanda]

PR Title: Migrate to Manifest V3 and Update Options Page

#Description:

This PR migrates the Chrome extension to Manifest V3 and updates the options page to ensure compatibility and improved

#functionality. The following changes have been made:

Manifest V3 Migration:

Updated manifest.json to use manifest_version: 3.
Replaced background scripts with service_worker.
Moved URL patterns from permissions to host_permissions.

#Options Page Update:
Changed options_page to options_ui in manifest.json.
Ensured options.html exists and handles URL parameters (e.g., ?firstTime).

#Content Security Policy:
Updated content_security_policy to comply with Manifest V3 requirements.

#General Improvements:
Verified the existence of all necessary files (e.g., options.html, icons).

#Ensured all functionalities work as expected after migration.

Testing

#Notes

Users need to manually enable "Allow access to file URLs" in the Chrome extension settings for file URL access.
The extension now requires Chrome version 88 or higher.

---

#Summary

This PR ensures that the Chrome extension is fully compatible with Manifest V3 and improves the options page functionality. Please review the changes and provide feedback.

Feel free to adjust the description as needed to better fit your project's context and any additional details you might want to include.

If you want this to be merged and needs changes let me know

---

If you feel like supporting me you can do that by:
https://buymeacoffee.com/aybanda

[user334]

Hey @aybanda!
It's awesome you've decided to help this project to move to MV3. Thanks for your contribution!

I wanted to ask if you've seen the previous PR here. The blocking thing there is that the extension is not only need to "just" switch to mv3, but know about the Chrome's tab grouping feature. So is your new code aware of such a function? Please check this out: #234 (comment)

And again, thanks for your effort! I really hope this PR would get merged.

[trekshcool]

I am having a little trouble trying to load this pull request I downloaded this branches zip from here - https://github.com/aybanda/MarvellousSuspender/tree/migrate-to-Manifest-V3

After that I tried to load the folder into chromes bata branch but I got the following error

After that I tried to go into the scr folder which has the manifest file to try to load it but then I got this error.

Any suggestions on what I am doing wrong here?

[Technetium1]

Thanks for this, consider marking it as a draft until it's been fully tested.

[ThisIsSammysAccount]

Thanks for your help. Regarding the loading issue, I believe the service_worker path for background.js in manifest.json needs to be changed to js/background.js so it can find the file. Also, a number of existing TMS functions in background.js were removed. I assume that was intentional given your comment "// Other functions and event listeners..." in place of the prior code, but let me know if I just missed something.

[trekshcool]

Thanks for your help. Regarding the loading issue, I believe the service_worker path for background.js in manifest.json needs to be changed to js/background.js so it can find the file. Also, a number of existing TMS functions in background.js were removed. I assume that was intentional given your comment "// Other functions and event listeners..." in place of the prior code, but let me know if I just missed something.

After changing the background.js to js/background.js the extension loaded with the following errors.

[trekshcool]

@aybanda How did you manage to test it and get no errors?

[AlexByte]

@trekshcool Why are you testing the extension in Windows Sandbox?

[trekshcool]

@AlexByte Because I dont want to install the beta branch on my actual pc and mess up all my v2 extensions and tabs and then have to go though the hassle of uninstalling and downgrading chrome and recovering all my data.

It shouldn't make a different anyway its essentially a VM.

[user334]

@trekshcool you can easily install a different branch of Chrome alongside your main one. Like a Dev or Canary. It'd be a completely separate browser and any mess that can happen there won't leak to the Stable.

But it's interesting that Windows now has such a feature. Here on macOS we don't have anything useful like this.

[AlexByte]

@trekshcool are you using a beta branch as the main one?

[trekshcool]

@AlexByte I am using the beta branch as it has manifest v3, current stable does not.

@user334 Yeah its a pretty new future and very easy to use, interesting that you can install both beta and main alongside one another didn't know that.

Have you guys managed to load the extensions or are you getting the same errors?

[AlexByte]

@trekshcool The stable version supports Manifest V3 and Manifest V2. Sandbox is an old feature from 2018.

Manifest V3 is supported generally in Chrome 88 or later

[trekshcool]

@AlexByte Wasn't it called something else before? I think they rebranded it. Either way I have now tested on stable too and its giving the same errors.

[AlexByte]

@trekshcool it wasn't rebranded.

[trekshcool]

@AlexByte Yup goggling around a bit your right, looks like I was misinformed by a youtube short.

[ThisIsSammysAccount]

Finally had a chance to check out the PR and take a look. To get the extension to load you need to run npm install and then npm run build, which will create a build directory with the unpacked extension and a zipped file. Part of the gruntfile moves backgrounds.js up a directory, which is why you were seeing path errors without running the build first. Unfortunately, once the extension is built and loaded it still has issues. Part of the migration to the service worker model in v3 requires replacing chrome.extension.getBackgroundPage(), which has not been done yet.
https://developer.chrome.com/docs/extensions/develop/migrate/api-calls?hl=en#replace-mv2-function

So, the good news is that the extension will load. The bad news, it doesn't work yet, and there are missing features as I previously noted. Until @aybanda has a chance to make updates this isn't ready for testing.

[trekshcool]

@aybanda have a look #197 (comment)

[trekshcool]

Its finally happening, chrome is now a/b testing disabling v2 extensions on the latest main chrome release.

For those of us who have the registry trick it will work for a few more months but for the rest the end is now.