Open
Bug 1701909
Opened 4 years ago
Updated 4 years ago
Account for tabTracker.activeTab being null when container-level isolation of extensions are enabled
Categories
(WebExtensions :: General, task, P5)
WebExtensions
General
Tracking
(Not tracked)
NEW
People
(Reporter: robwu, Unassigned)
References
(Blocks 1 open bug)
Details
The extension framework retrieves the "current / active" tab in several places, e.g. via tabTracker.activeTab
, With bug 1683058, that tab may be inaccessible, and consequently the tab may be null. We should resolve this, either by preventing the code from being reached when an extension doesn't have the permission for the tab, or by checking the condition (tab being null) more explicitly.
Reporter | ||
Updated•4 years ago
|
Severity: -- → N/A
Priority: -- → P5
You need to log in
before you can comment on or make changes to this bug.
Description
•