Component

Full Dashboard

Performance Monitor Version

1.1.0

SQL Server Version

SQL Server 2019 CU32

Windows Version

Windows Server 2025 Standard

Describe the Bug

In the Procedure Execution History window (and likely in all application grids), column resizing works correctly when dragging the column edge.
However, when performing a double‑click on the column header border (to auto‑size the column), the application performs two actions:

1. The column is automatically resized — correct behavior
2. The double‑click is also interpreted as a double‑click on the selected row, which opens the Procedure Execution History window — incorrect behavior

This happens even though the user is double‑clicking in the header area, not inside a data row.

Steps to Reproduce

1. Open the Procedure Execution History window (or any other window in the application that contains a data grid).
2. Move the mouse to the border between two column headers to get the resize cursor.
3. Double‑click on the column header border to auto‑resize the column.
4. Observe that:

• The column width is correctly auto‑adjusted (expected).
• BUT the application also triggers the row double‑click event, opening the Procedure Execution History window for the currently selected row (unexpected), even though the click was performed in the header, not on a data row.

Expected Behavior

• A double‑click on a column header border should only auto‑resize the column.
• It should not trigger the row double‑click event.
• Header‑level interactions must be isolated from row‑level events to prevent unintended navigation.

Actual Behavior

Double‑clicking the border between column headers triggers both:

• Auto‑resize of the column (expected)
• The row double‑click event, which opens Procedure Execution History even though the click occurred in the header, not in a row.

Error Messages / Log Output

Screenshots

No response

Additional Context

No response