search

SAP / openui5

OpenUI5 lets you build enterprise-ready web applications, responsive to all devices, running on almost any browser of your choice.
http://openui5.org
Apache License 2.0
2.92k stars 1.23k forks source link

sap.m.Menu control requires focus lost (klicking into space outside the menu) in order to close #4033

Open s4711 opened 2 months ago

s4711 commented 2 months ago

OpenUI5 version: 1.122 (3 versions)

Browser/version (+device/version): safari on ipad (issue is related especially to a tablet device)

Any other tested browsers/devices(OK/FAIL):

URL (minimal example if possible): https://sapui5.hana.ondemand.com/#/entity/sap.m.Menu Menu

User/password (if required and possible - do not post any confidential information here): n/a

Steps to reproduce the problem:

  1. open the menu
  2. in order to close the menu it is necessary to klick outside the menu
  3. a klick outside the menu (attachment: klick e.g. on a list item to the left)

What is the expected result? menu closes ('focus lost' klick event is not propagated)

What happens instead? menu closes and the event bubbles and raises a click event (e.g. on the list item ... which leads to a navigation to a detail screen) ISSUE is that the user just wants to close the menu - but unintentionally executes the 'next' action

Any other information? (attach screenshot if possible) On a phone the menu will render as a 'Action' sheet on the bottom of the screen - the rest of the screen is not active and the sheet only can be closed explicitly with the close button (fine). But e.g. on a tablet the menu shows the above behaviour - and a tablet has limited space (compared to desktop) - Now in our application the screen contains lots of clickareas and limited 'empty' space - so the user 'just' wants to close the menu - but in addition to the 'menu close' the klick leads e.g. to a screen navigation.

PetyaMarkovaBogdanova commented 2 months ago

Hello @s4711 , Thank you for sharing your enhancement proposal. I've created an internal incident DINC0136369. The status of the issue will be updated here in GitHub. Regards, Petya Markova. (UI5 Dispatcher)