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

V17: TieredMenu and CascadeSelect malfunction in p-dialog #16502

Closed
romainbar opened this issue Oct 8, 2024 · 1 comment
Closed

V17: TieredMenu and CascadeSelect malfunction in p-dialog #16502

romainbar opened this issue Oct 8, 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

@romainbar
Copy link

Describe the bug

Opening TieredMenu from p-dialog, menu starts hundreds of pixels to right of clicked location.
CascadeSelect does not scroll when higher than screen, bottom options are unreachable.
Standard p-dropdown works fine but does not have submenus.

Environment

Angular 18 + PrimeNg 17

Reproducer

No response

Angular version

18.2.7

PrimeNG version

17.18.11

Build / Runtime

TypeScript

Language

TypeScript

Node version (for AoT issues node --version)

22.9.0

Browser(s)

Chrome 129

Steps to reproduce the behavior

  1. Open p-dialog, click on TieredMenu button, menu consistently opens hundreds of pixels to right of clicked location.
  2. Open p-dialog, click on CascadeSelect button, with option list going below browser bottom it's impossible to scroll to hidden options.

Expected behavior

  1. Menu shall open at clicked location, as when opening outside dialog.
  2. User shall be able to reach all menu options, CascadeSelect shall allow scrolling through options, as when opening outside dialog.
@romainbar romainbar added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label Oct 8, 2024
@nckirik
Copy link

nckirik commented Oct 8, 2024

i my case, setting appendTo to body solved the problem

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

3 participants