[Bug - Edge Addons] SidePanel (Sidebar) Bug/Issue in Edge Extension

[jaissam10]

Describe the bug We are planning to introduce new features in the side panel using browser extension. However, due to the following issue, we are unable to proceed

Problem Statement: When the side panel is launched on one webpage, it opens on all other webpages. Similarly, closing it results in the side panel being closed across all pages/tabs. According to Microsoft’s documentation on the sidebar, the sidebar can be opened using the following Chrome API: chrome.sidePanel.open() This API accepts a parameter windowId or tabId depending on the context in which the sidebar should be enabled. In our use case, when we use chrome.sidePanel.open({ tabId: tab.id }), the side panel unexpectedly opens in all open tabs, creating only a single shared instance. When closed, it closes on all tabs simultaneously. This behavior is inconsistent with the documentation. In contrast, on the Chrome browser, the same code works as expected—it creates a separate instance of the side panel for each tab.

To Reproduce Take any sample extension which has sidepanel and open sidepanel and observe other tabs.

Expected behavior It should create a separate instance of the side panel for each tab.

Desktop (please complete the following information):

• OS: [e.g. iOS]- MacOs
• Browser [e.g. chrome, safari] - Microsoft Edge
• Version [e.g. 22] - 133.0.3065.69

[ManikanthMSFT]

Hi @jaissam10, thank you for contacting us. We are looking into this and will let you know as soon as we have an update.

[jaissam10]

@ManikanthMSFT I'd appreciate it if you could share an update you are having as of now.

[ManikanthMSFT]

Hi @jaissam10, we would like to assure you that this issue is a top priority for our team. We are actively working on it and will provide you with updates as soon as we have more information.

[CrazyBoyM]

any update now?

[ManikanthMSFT]

Hi @CrazyBoyM, @jaissam10, thank you for your patience. We have received an update from our team and are pleased to inform you that the fix is in the canary and will be completed by the end of next week.

We appreciate your understanding during this time and will keep you informed of any changes.

[jaissam10]

@ManikanthMSFT Glad to hear that this issue has been fixed! Could you share the Canary version in which this fix will be available? Also, do we have an expected release date for the production Edge build?

[ManikanthMSFT]

Hi @jaissam10, we would like to provide you with the latest updates on the Microsoft Edge builds.

The Canary version is now available: 136.0.3187.0. Additionally, the expected release date for the production Edge build is scheduled for next week. Should there be any changes in the timeline, we will promptly inform you.

Below are the details for the latest Edge Dev builds:

Windows (ARM64, x64, x86): 136.0.3193.0 macOS (Universal, x64): 136.0.3193.0 Linux: Pending Release Android (ARM64): 136.0.3194.0 iOS (ARM64): 136.0.3194.0 Please let us know if you need any further information.

[jaissam10]

@ManikanthMSFT Apologies for the confusion. I wanted to ask in which version of Edge Canary this fix will be available. Also, what is the planned release date for the production version that includes this fix, ensuring that each tab has a separate instance of the side panel when opened using the tabId parameter?

Additionally, is there any release note or documentation from Microsoft that details this fix?

[jaissam10]

@ManikanthMSFT Apologies for the confusion. I wanted to ask in which version of Edge Canary this fix will be available. Also, what is the planned release date for the production version that includes this fix, ensuring that each tab has a separate instance of the side panel when opened using the tabId parameter?

Additionally, is there any release note or documentation from Microsoft that details this fix?

@ManikanthMSFT Can you please update on this?

[ManikanthMSFT]

Hi @jaissam10, sorry for the confusion. We understand that when the side panel is launched on one webpage, it opens on all other webpages, and closing it results in the side panel being closed across all pages/tabs. This behavior is inconsistent with Microsoft's documentation, which states that the chrome.sidePanel.open() API should create a separate instance of the side panel for each tab when using chrome.sidePanel.open({ tabId: tab.id }).

Our engineering team has confirmed that this behavior is currently by design and is a known limitation in Edge. The team will re-evaluate this issue in the upcoming C2 cycle and will hopefully prioritize it for resolution. We appreciate your patience and understanding as we work towards improving this functionality.

If you have any further questions or need additional assistance, please do not hesitate to reach out.

[Rahul-Bauri]

Hi @jaissam10

Closing this issue & tracking it here (https://github.com/microsoft/MicrosoftEdge-Extensions/issues/222#issuecomment-3132768143), as it appears to be related.

[jaissam10]

Hey @Rahul-Bauri and @G-u-r-j-e-e-t , Is there any update on the ticket?

[Rahul-Bauri]

Hi @jaissam10

Please refer to #222 for further updates regarding this bug. I’ll post any new information from the internal team in that ticket as soon as it becomes available. Thank you for your understanding!