sap.ui.table.Table - columnMenu malfunction after view navigation

[Cdabsgmbh]

What is the issue and how can we reproduce it?

When using multiple sap.ui.table.Table instances across different views in a single application, the "Unfreeze" option in the column menu can become unavailable. This issue occurs after a user freezes columns in a table in one view and then navigates to a new view and freezes a column in a different table.

Steps to Reproduce:

1. View A contains a sap.ui.table.Table. Freeze one or more columns in this table.
2. Navigate to View B, which contains a separate sap.ui.table.Table.
3. Freeze a column in the table in View B.
4. Open the column menu for any column in the table in View B.

Observed Behavior
The "Unfreeze Columns" option is missing from the column menu in View B. As a result, it is impossible to unfreeze any columns in this table. Interestingly, the table in View A is not affected, and its column menu continues to function correctly.

Technical Analysis
It appears there may be an issue with how the column menu's state is invalidated or reset when a user navigates between views.

When a column is frozen under normal circumstances, the invalidateColumnMenu() method is called twice, correctly updating the menu's state to include the unfreeze option for the next time it's opened (see Picture 1 and Picture 2). However, when the steps to reproduce are followed, this process seems to fail for the table in the second view, even though the same code paths are executed.

This suggests that some internal state or cached information related to the column menu is not being properly cleared or is being incorrectly shared between the different sap.ui.table.Table instances, leading to a stale or improperly rendered menu.
I assume that this might be an issue in internal handling of the invalidation of the columnMenu.

Picture 1:

Picture 2:

Impact
This bug prevents users from unfreezing columns, which can lead to a poor user experience and limit their ability to interact with table data as expected.

Which OpenUI5 version is your project targeting?

1.120.24

Is the issue device- or browser-specific?

No

Confirmation

• I have searched the existing issues and reviewed the relevant documentation as well as the API reference.
• I am not disclosing any internal or sensitive information.

[boghyon]

Could you share a minimal reproducible example (MRE)? E.g. through this Plunker template: click on "Fork", edit to create an MRE, save, and share the new URL. Thanks!