You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For enterprise process excellence/compliance/governance/security browser extensions, requiring user interaction undermines the effectiveness of the extension
For enterprise productivity extensions (e.g., contact center agent assist), requiring user interaction increases the amount of training required for employees
Example Use Cases
Automatically show relevant policies related to content on the page (e.g., state/locality-specific policies)
Automatically show a checklist in the side panel
Automatically show a decision tree in the side panel
Automatically open a translation side panel when a foreign language is detected on the page
Automatically open a reporting form if a trust and safety keyword is detected on a page
Automatically open a grammar/writing sidebar on specific sites like Google Docs, MS Word, etc.
Options:
Allow programmatically opening the side panel if the extension has <all_urls> permission
Always allow programmatically opening the side panel
Introduce a new optional permission granting permission to automatically open the side panel
Discussion
Including the capability under the <all_urls> permissions could make sense, as compliance/governance/security extensions would likely have that permission already, and it also already triggers a more in-depth store review (at least for Chrome)
Firefox's sidebarAction.open() method requires user interaction. Additionally it is also possible to open the sidebar by default once after install, with the "open_at_install": true option in the manifest.
Would like to add to this request, that starting with Chrome 118+ it is possible to programmatically open the popup (chrome.action.openPopup). For this no user interaction is required.
Since that works without user interaction, I would expect that the chrome.sidePanel.open also would not require it.
Context
sidePanel.open()
method supports programmatically opening in response to user interaction in ChromeExample Use Cases
Options:
<all_urls>
permissionDiscussion
<all_urls>
permissions could make sense, as compliance/governance/security extensions would likely have that permission already, and it also already triggers a more in-depth store review (at least for Chrome)Related Features/Permissions/APIs
action.openPopup
does not require user interaction in Chrome<all_urls>
permissionThe text was updated successfully, but these errors were encountered: