Closed Bug 1956860 Opened 27 days ago Closed 20 hours ago

Make extension's management page accessible via commands

Categories

(WebExtensions :: Frontend, enhancement)

enhancement

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: erosman, Unassigned)

Details

WebExtensions often need to warn users to enable "Run in Private Windows", especially when the the API demands it as in proxy.settings.

In Chrome, extension’s management page can be reached via chrome://extensions/?id=...

Subsequent to Bug 1538451, it would be useful to have a similar process to open extension's management page.

An extension can call browser.runtime.openOptionsPage() and show instructions to switch to the right tab and toggle access.

Although it may be feasible to add a special method or option to open the generic add-on details page, there would not be a guarantee that the opened tab is where the "Run in Private Windows" setting is shown. When discussed in the WECG, there was no appetite at other browser vendors to offer the ability for extensions to trigger the "run in private windows" request either.

An extension that wishes to guide the user towards enabling the setting can use browser.runtime.openOptionsPage() to open the extension settings page and then in-content show instructions on enabling access if needed (when browser.runtime.isAllowedIncognitoAccess() reports false). If an extension wanted to use options_ui.open_in_tab, they could also use browser.tabs.create or browser.tabs.update to navigate the options page to the new tab.

Status: NEW → RESOLVED
Closed: 20 hours ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.