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

p-tieredMenu responsive: We've to tap twice to open the submenu #16035

Closed
UlricW opened this issue Jul 16, 2024 · 1 comment
Closed

p-tieredMenu responsive: We've to tap twice to open the submenu #16035

UlricW opened this issue Jul 16, 2024 · 1 comment
Labels
Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible

Comments

@UlricW
Copy link

UlricW commented Jul 16, 2024

Describe the bug

In responsive mode (like ipad pro for example), when clicking on a menu that contains submenu, we've to tap 2 times to open the submenu overlay, the first tap focus the menu, and the second one open the overlay

we can reproduce it easily by opening the p-tieredmenu stackblitz (my example is the routing one), we activate the responsive mode from chrome, and select ipad pro as device

Environment

Windows 11, PrimeNG 17.8.1, angular 17.1.0

Reproducer

No response

Angular version

17.1.0

PrimeNG version

17.8.1

Build / Runtime

Angular CLI App

Language

TypeScript

Node version (for AoT issues node --version)

18.18.2

Browser(s)

Chrome

Steps to reproduce the behavior

we can reproduce it easily by opening the p-tieredmenu stackblitz (my example is the routing one), we activate the responsive mode from chrome, and select ipad pro as device

Expected behavior

The submenu overlay shoud be opened on the first tap

@UlricW UlricW added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label Jul 16, 2024
@mertsincan
Copy link
Member

Hi,

So sorry for the delayed response! Improvements have been made to many components recently, both in terms of performance and enhancement. Therefore, this improvement may have been developed in another issue ticket without realizing it. You can check this in the documentation. If there is no improvement on this, can you open a new issue so we can include it in our roadmap?

Thanks a lot for your understanding!
Best Regards,

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible
Projects
None yet
Development

No branches or pull requests

2 participants