Steps To Reproduce
Install Bitwarden
$ExtensionID = 'nngceckbapebfimnlniiiahkandclblb' If ($IsWindows) { # https://reg2ps.azurewebsites.net/ If ((Test-Path -LiteralPath 'HKCU:\SOFTWARE\Policies\Google\Chrome\ExtensionInstallForcelist') -NE $True) { New-Item 'HKCU:\SOFTWARE\Policies\Google\Chrome\ExtensionInstallForcelist' -Force -EA SilentlyContinue } New-ItemProperty -LiteralPath 'HKCU:\SOFTWARE\Policies\Google\Chrome\ExtensionInstallForcelist' -Name '1' -Value "$ExtensionID" -PropertyType String -Force -EA SilentlyContinue } ElseIf ($IsLinux) { $Path = '/etc/chromium/policies/managed/yourextension_policy.json' New-Item -ItemType File -LiteralPath ((Get-Item "$Path").Parent) -Name ([System.IO.Path]::GetFileName("$Path")) Set-Content -LiteralPath "$Path" -Value @" { 'ExtensionInstallForcelist': [ '$ExtensionID;https://clients2.google.com/service/update2/crx', '$ExtensionID' ] } "@ }
Enable Bitwarden
Enable the Side Panel
Attempt to switch to Bitwarden
Expected Result
Bitwarden should be available in the Side Panel.
Actual Result
It is not.
Additional Context
https://9to5google.com/2023/05/26/chrome-extensions-side-panel/
Operating System
Windows, macOS, Linux
Operating System Version
cpe:/o:opensuse:tumbleweed:20230803
Web Browser
Chrome
Browser Version
google-chrome-unstable-117.0.5927.0
Build Version
https://www.crx4chrome.com/crx/31978/
Issue Tracking Info
- I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn’t use fields like “assigned”, “milestone”, or “project” to track progress.
We support the side panel/bar on Firefox and Opera. I wasn’t aware that Chrome had a usable side panel feature. From what I read, it seems like they removed it in recent versions?
1 Like
@kspearrin, developer.chrome.com/docs/extensions/reference/api/sidePanel#availability
lists:
-
Chrome 144+
-
MV3+
However, in google-chrome-canary-134.0.6972.0-1.x86_64
, chrome://flags/#side-panel
doesn’t exist anymore, and remaining purpose-specific sidebars appear, based upon how they’re invoked in the GUI, to be inextensible. [1] I presume the documentation is out-of-date, but I’m no extension developer.
I think you’re right.
The undermentioned may be relevant!