Default Firefox to MV3

[aklinker1]

Feature Request

Before this can happen, the following changes are required:

• MV3 out of experimental status v109 added MV3 support
• fix: Generate valid manifest for Firefox MV3 #229
• Dev mode support: https://bugzilla.mozilla.org/show_bug.cgi?id=1864284

Is your feature request related to a bug?

#226

[aklinker1]

Firefox MV3 dev mode (wxt -b firefox --mv3) does not work, see https://bugzilla.mozilla.org/show_bug.cgi?id=1864284 for more details. You have a two options:

1. Use --mv2, the default, instead when developing against firefox wxt -b firefox --mv2
2. Build for production, wxt build -b firefox --mv3, and load the extension manually into Firefox to test it

[dvlden]

I have released my extension on Firefox add-ons for Desktop and Android as MV3.
Instantly regretted it.

• Requires users to give extension access to all websites. It's not automatically allowed as in MV2.
• Firefox Android really lacks MV3 compatibility

Releasing soon MV2 for Firefox instead as it resolves both of the issues from above.

Leaving this as a note. Firefox is not ready, maybe in a few years.

[aklinker1]

Yeah, I just released my rewrite as MV3 extension and the permissions are weird... Probably more secure, but less user friendly, for sure. I'm not supporting Android, so that's not a problem for me.

I'm gonna close this issue for now so I don't have to keep looking at it.

[yunsii]

But https://wxt.dev/guide/multiple-browsers.html and development console have no information about this 😂 I spend so many time to debug why firefox add-on with mv3 not work...

[aklinker1]

WXT should exit with an error message when you try and run wxt -b firefox --mv3

[yunsii]

WXT should exit with an error message when you try and run wxt -b firefox --mv3

Really? Why I do not encounter any error message?

[aklinker1]

Huh 😖

[aklinker1]

@yunsii Can you add this log to your project? Inside node_modules/wxt/dist/cli.js, do a ctrl+F for "Dev mode does not support Firefox MV3" and add this log before the if statement:

console.log(wxt.config.browser, wxt.config.manifestVersion)

Then re-run the command that's failing and let me know what is logged?

[yunsii]

@aklinker1 It seems a bug with WSL?

wxt/src/core/runners/wsl.ts

Lines 8 to 22 in 86b7162

	export function createWslRunner(): ExtensionRunner {
	return {
	async openBrowser() {
	wxt.logger.warn(
	`Cannot open browser when using WSL. Load "${relative(
	process.cwd(),
	wxt.config.outDir,
	)}" as an unpacked extension manually`,
	);
	},
	async closeBrowser() {
	// noop
	},
	};
	}

And why exit with an error message at beginning of dev command?

[aklinker1]

It seems a bug with WSL?

@yunsii This is intentional. web-ext doesn't work well in WSL: mozilla/web-ext#2108 (comment)

[yunsii]

@aklinker1 So how about exit with an error message at start of dev command?

[aklinker1]

No, dev mode still works, just can't open the browser automatically. For Firefox mv3, it just doesn't work, which is why it exits

[yunsii]

Firefox MV3 dev mode (wxt -b firefox --mv3) does not work, see bugzilla.mozilla.org/show_bug.cgi?id=1864284 for more details. You have a two options:

1. Use --mv2, the default, instead when developing against firefox wxt -b firefox --mv2
2. Build for production, wxt build -b firefox --mv3, and load the extension manually into Firefox to test it

So it is a upstream bug, use this workaround for now.

[dword-design]

@aklinker1 Could it be that this is working now? I tried it with vite-plugin-web-extension, Firefox MV3, a background script and a content script. Updating the content script also updates in the browser in dev mode.

[aklinker1]

@dword-design nope, still not working. HTML pages are broken, not content scripts.