Open tianhuil opened 1 year ago
this would be awesome
Yes, this would be so good!
chrome 123
> removed the side panel button? Hey guys; question: when I do chrome.sidePanel.setPanelBehavior({ openPanelOnActionClick: true })
, I get cannot read property ... of undefined (reading setPanelBehavior)
.
Is there any solution/workaround for that?
@tianhuil did you ever get the side panel working for a non-chrome browser?
Hey guys; question: when I do
chrome.sidePanel.setPanelBehavior({ openPanelOnActionClick: true })
, I getcannot read property ... of undefined (reading setPanelBehavior)
.Is there any solution/workaround for that?
I'm running into the same issue right now. Looks like sidePanel doesn't exist on my chrome object for some reason, even though I've set permissions: [ "sidePanel" ]
in my manifest.json
. Did you ever figure this out?
Did you ever figure this out?
It's been a while, but I quickly gave up on Plasmo since, IMO, it's trying to do too much abstraction, which ... concrete example here ... doesn't seem to work!
How do you envision this feature/change to look/work like?
Currently, running
chrome.sidePanel.setPanelBehavior({ openPanelOnActionClick: true })
inbackground.ts
is the only way to toggle a side panel when the user clicks the browser extension in Chrome. This isn't very browser-independent. Can we create a generic option that enables/disables this behavior across all browsers (e.g. safari, firefox, chrome, etc ...)?What is the purpose of this change/feature? Why?
See above.
(OPTIONAL) Example implementations
No response
(OPTIONAL) Contribution
Verify canary release
plasmo
canary releaseCode of Conduct