Issue Summary

In Jira and Confluence, when using Microsoft Edge on Windows, the left sidebar can initially be resized by dragging its border. However, after some time, the sidebar becomes stuck and is no longer resizable. When this happens, the sidebar may occupy almost half of the screen, severely interrupting work because it cannot be reduced or adjusted, making it difficult or impossible to use the main content area.

The customer used the most recent browser version. Browser details:

• Microsoft Edge version: 142.0.3595.76 (Official build) (64-bit)

Steps to Reproduce

1. Open Microsoft Edge for Windows (Version 142.0.3595.76 (Official build) (64-bit)).
2. Navigate to a Jira or Confluence page in the site.
3. Use the mouse to resize the left sidebar (navigation panel) by dragging its border.
4. Continue working for some time, periodically resizing the left sidebar (e.g., switching between pages, projects/spaces, or views and adjusting the sidebar width as needed).
5. Observe that at some point the left sidebar becomes stuck at its current width and can no longer be resized.

Expected Results

• The left sidebar in Jira and Confluence should always remain resizable.
• Dragging the sidebar border should consistently change its width, regardless of how long the browser has been open or how many times it has been adjusted.
• The user should never end up in a state where the sidebar is frozen at a width that blocks a significant portion of the screen.

Actual Results

• After some time using Jira and/or Confluence in Microsoft Edge for Windows, the left sidebar stops responding to resize attempts.
• Dragging the sidebar border no longer changes its width.
• The sidebar can become stuck when it takes almost half of the screen, leaving limited space for the main content and making normal work very difficult or impossible.

Additional customer observations:

• When using InPrivate/incognito mode in Microsoft Edge, the issue does not occur; the sidebar remains resizable.
• Clearing cache in a normal (non-incognito) Edge profile does not resolve the issue; the problem persists.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available