Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

sap.m.Tree Selecting/unselecting nodes is impossible when context menu is left #4200

Open
GuillaumedesPommareSAP opened this issue Jan 31, 2025 · 1 comment

Comments

@GuillaumedesPommareSAP
Copy link

Hello,

We identified an issue during our testing.
We are using a sap.m.Tree configured in multi selection as well as defining a context menu.
Step1: you navigate to a node and you activate the context menu using the keyboard shortcut (Shift-F10)
Step 2: you leave the context menu by clicking somewhere else. You must not select an entry, you must not press Esc key
Step 3: you navigate to another node and select it

Observations: all nodes between the node where you have opened the menu, and the last one, are selected.
Selection is locked.

You can leave selection by pressing Esc or reload the page

Most probably the keyboard shortcut Shift F10 conflict with multi selection starting with Shift, and the Shift modifier is not removed when leaving the menu.

This issue can easily be reproduced. You go to an official sample: https://sapui5.hana.ondemand.com/1.132.1/#/entity/sap.m.Tree/sample/sap.m.sample.TreeIcon
The version could be current LTS 1.120.X up to current 1.132.1
You must edit the sample, adding mode="MultiSelect" in the Page.view.xml, in the Tree XML Node
You must also active the context menu switch in the Tree preview, as it is off by default in the sample

You can now test it: select Node1-1-1 clicking on the combobox
Press Shift + F10
Click anywhere else
Select Node1-2
All nodes starting from top are selected. Selection cannot be undone

Image

We expect a fix on current UI5 LTS, 1.120.X.

Thanks.
Guillaume

@i556484
Copy link
Member

i556484 commented Jan 31, 2025

Hello @GuillaumedesPommareSAP,
Thank you for sharing this finding. I've created an internal incident DINC0398055. The status of the issue will be updated here in GitHub.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants