Add `activeTab` as permission for `tabs.captureVisibleTab` API
Categories
(WebExtensions :: General, enhancement, P2)
Tracking
(firefox126 fixed)
Tracking | Status | |
---|---|---|
firefox126 | --- | fixed |
People
(Reporter: juraj.masiar, Assigned: willdurand)
References
(Blocks 1 open bug)
Details
(Keywords: dev-doc-complete, Whiteboard: [addons-jira])
Attachments
(1 file)
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:104.0) Gecko/20100101 Firefox/104.0
Steps to reproduce:
From what I can see in the docs, both Chrome and Safari (see compatibility table) requires only activeTab
permission to capture the tab.
Why is this different in Firefox?
The problem is, that even super simple addons that needs to work with screenshots now requires this huge permission that nobody likes.
And I see no reason why. The addon with active:tab
has already full HTML access, so what else is there to hide?
Thanks :)
Comment 1•2 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Firefox::Tabbed Browser' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Comment 2•2 years ago
|
||
Thank you for submitting this enhancement. I'll set this to NEW and waiting for the developer's opinion about it.
Reporter | ||
Comment 3•2 years ago
|
||
Thanks!
Just to clarify and summarize my original post:
- currently addons needs
<all_urls>
permission to usetabs.captureVisibleTab
- I'm suggesting adding also
activeTab
permission - Chrome and Safari already supports
activeTab
permission for this API
Comment 4•2 years ago
|
||
I coincidentally came across this bug when searching for captureVisibleTab
. I'm moving this to the right component so that it can be seen by the right developers (extension team).
Comment 5•2 years ago
|
||
This sounds reasonable.
Some additional considerations: we now treat activeTab
as only covering same-origin iframes, to better align with new host permission controls and user expectations, but change in this bug would mean we're muddling the the water again. I think the compromise is still worth it here, because (unlike other considerations with different-origin iframes) this would capture only what is visible (and "obvious") in the tab.
Updated•2 years ago
|
Assignee | ||
Comment 6•7 months ago
|
||
Updated•7 months ago
|
Updated•7 months ago
|
Updated•7 months ago
|
Comment 8•7 months ago
|
||
bugherder |
Assignee | ||
Updated•6 months ago
|
MDN content changes are ready for review
- MDN content Enable activeTab permission for tabs.captureVisibleTab #33841
- BCD Note about activeTab permission for tabs.captureVisibleTab #23215
Assignee | ||
Updated•5 months ago
|
Description
•