Side Panel Opens with Stale Configuration Despite Updated chrome.sidePanel.setOptions Calls

Question

We have encountered a situation in Microsoft Edge where an extension uses the chrome.sidePanel APIs (chrome.sidePanel.setOptions and chrome.sidePanel.open) to dynamically update the side panel’s URL and associated parameters. Despite confirming that the updated configuration is set correctly, the side panel occasionally opens with outdated (or “stale”) settings. This inconsistent behavior disrupts the expected workflow, as the side panel URL should always reflect the latest parameters.

Environment Details

• Operating System: (e.g., macOS Sequoia v15.2 or Windows 11)

• Browser Version: Microsoft Edge (latest stable release)

• Extension: Uses standard Chrome/Edge extension APIs (sidePanel)

Issue Description

When the extension button is clicked, the following sequence occurs:

1. chrome.sidePanel.setOptions updates the URL, including parameters such as the current tabId.
2. chrome.sidePanel.open is then called to display the side panel.

Although the extension’s code confirms that new options are correctly assigned before calling chrome.sidePanel.open, the panel sometimes appears with older options (including stale URL parameters). This suggests that chrome.sidePanel.open might be using previously cached settings rather than the newly set values.

Steps to Reproduce

1. Install the extension in Microsoft Edge.
2. Navigate to any webpage and click the extension’s button to open the side panel.
3. Observe the parameters passed to chrome.sidePanel.setOptions (for instance, a URL containing the active tabId).
4. Call chrome.sidePanel.open immediately after verifying the options are set.
5. Check the loaded content within the side panel.

Actual Result: The side panel may open using outdated or stale URL parameters and settings on a new tab for the first time.

Expected Result: The side panel should reliably open using the newly configured options every time.

Additional Observations

• This behavior appears tied to the Chrome/Edge extension APIs rather than the extension’s own logic, since logging confirms the correct parameters are passed.

• Re-verifying or re-calling setOptions just prior to opening does not consistently resolve the issue.

• No console or error message is displayed that indicates why the older configuration sometimes persists.

Request

We kindly request that the Microsoft Edge team investigate whether this is a browser-level bug related to the chrome.sidePanel APIs. If you have any guidance on potential workarounds or a plan for a fix, please let us know. We are happy to provide additional logs, steps, or demonstrations to assist in reproducing the issue.

Thank you for your time and assistance!