1800421 - tabs.captureTab and tabs.captureVisibleTab does not work on MV3

Status: NEW

(WebExtensions :: General, defect, P2)

Description

[po932bbt]

Attachment: sample-addon-test.zip

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:108.0) Gecko/20100101 Firefox/108.0

Steps to reproduce:

Created an addon with <all_urls> added on the host_permission and tried to call browser.tabs.captureTab and browser.tabs.captureVisibleTab.

On this bug report I have made an attachment of two similar extension whose only mainly difference is that one is using MV2 and the other is MV3. The codebases aside from that are identical.

Actual results:

It returned an error where both methods are undefined

Expected results:

browser.tabs.captureTab and browser.tabs.captureVisibleTab should be accessible.

Comment 1

[Alex Cornestean]

Hello,

I reproduced the issue on the latest Nightly (109.0a1/20221115214157), Beta (108.0b2/20221115200658) and Release (107.0/20221110173214) [after flipping the extensions.manifestV3.enabled pref to true in order to be able to install MV3 extensions] under Windows 10 x64 and Ubuntu 16.04 LTS.

After navigating to a random page, I clicked the extension toolbar icon and then on the “Capture” button from the pop-up. With the MV2 extension, the “Does it work” status changed to Yes, while for the MV3 extension it changed to No.

I did not, however, see any of the mentioned errors in either the web console, browser console or the extension console.

Comment 2

[BugBot [:suhaib / :marco/ :calixte]]

The severity field is not set for this bug.
:mixedpuppy, could you have a look please?

For more information, please visit auto_nag documentation.

Comment 3

[po932bbt]

Just poking this ticket and reporting that as of Firefox 110.0b2, it still doesn't work.

Comment 4

[BugBot [:suhaib / :marco/ :calixte]]

The severity field is not set for this bug.
:mixedpuppy, could you have a look please?

For more information, please visit auto_nag documentation.

Comment 5

[Gregory Pappas [:gregp]]

The MV3 test case in comment 0 runs without issue when I remove "permissions": ["<all_urls>"] from the schema, or when I manually enable Access your data for all websites in about:addons

So, it seems this is just inconvenient UX, not exactly a bug. I think we should gate captureVisibleTab behind activeTab and leave captureTab as is.

Comment 6

[po932bbt]

I think one of the issues here is that "<all_urls>" permission has been moved to host_permissions which caused all of these permission problem. I do not agree though that this is just an inconvenient UX bug as the "<all_urls>" has been explicity defined in the host_permission of the mv3 addon so theoretically, the captureVisibleTab and captureTab should work.

Although I do agree that we should gate captureVisibleTab on activeTab for MV3 moving forward.