Vivaldi not implementing sidepanels the way Chrome does?

[Rajat Paharia]

My extension makes use of the sidepanel, and in particular opens a new tab-specific instance of the sidepanel for each tab using code like this:

chrome.action.onClicked.addListener((tab) => {

chrome.sidePanel.setOptions({

tabId: tab.id,

path: 'sidepanel.html',

enabled: true

});

chrome.sidePanel.open({"tabId": tab.id});

});

This works great in Chrome, but in Vivaldi (which is also based on Chromium) it appears to be ignoring the "tabId" argument to sidePanel.open, so there is just one sidepanel being opened for all tabs. This breaks a bunch of my code which is expecting tab-specific side panels. 

Does anyone have any experience with Vivaldi or insight into this? 

thanks! - rajat

[Rajat Paharia]

Out of curiosity I just tried my extension in Edge and am noticing that it is also ignoring tab-specific sidepanels. 

If close the sidepanel on one tab, it closes on all of them. 

If I have the sidepanel open on a tab and then open a new tab, the opening of the new tab closes the sidepanel everywhere.

Are tab-specific sidepanels a Chrome-only thing? 

- rajat

[yoophoon wong]

https://github.com/GoogleChrome/chrome-extensions-samples/issues/982#issuecomment-1689919503    take a look , this issue seems caused by property sidepanel:{default_path:xxx},if the property was defined in manifest the sidepanel opened would be global one, try to comment the property

another issue is the sidepanel can't keep the accessable status or open automatically,this is what i'm facing...

[Rajat Paharia]

Thanks Yoophoon. I don't have the property defined in the manifest (and everything works fine in Chrome, just not in Vivaldi or Edge), so I think it must be something else...