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

The dropdown menu does not open upwards despite the limited space in the window. #14056

Closed
Chaoci opened this issue Nov 8, 2023 · 3 comments
Closed
Labels
Resolution: Stale Issue or pull request is inactivity and unfortunately it will be *closed* if there is no response Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible

Comments

@Chaoci
Copy link

Chaoci commented Nov 8, 2023

Describe the bug

In version 16.0.2, the dropdown could correctly determine the window space to display the menu. However, in the current version (16.7.1), this feature is missing. If I downgrade the version, the patchValue method does not work correctly with the dropdown, which is why I updated to the current version (16.7.1).

Environment

primeNG version: 16.7.1

Reproducer

No response

Angular version

16.2.9

PrimeNG version

16.7.1

Build / Runtime

TypeScript

Language

TypeScript

Node version (for AoT issues node --version)

20.5.0

Browser(s)

No response

Steps to reproduce the behavior

No response

Expected behavior

No response

@Chaoci Chaoci added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label Nov 8, 2023
@asiro85
Copy link

asiro85 commented Nov 10, 2023

Also experiencing the same problem with paginators at the end of a page. The workround was to use paginatorDropdownAppendTo="body" to force the dropdown menu not get cut by the end of the page.

Copy link

This issue has been automatically marked as stale. If this issue is still affecting you with the latest version, please leave any comment, and we will keep it open. We are sorry that we have not been able to prioritize it yet. If you have any new additional information, please include it with your comment!

1 similar comment
Copy link

This issue has been automatically marked as stale. If this issue is still affecting you with the latest version, please leave any comment, and we will keep it open. We are sorry that we have not been able to prioritize it yet. If you have any new additional information, please include it with your comment!

@github-actions github-actions bot added Resolution: Stale Issue or pull request is inactivity and unfortunately it will be *closed* if there is no response labels Dec 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Resolution: Stale Issue or pull request is inactivity and unfortunately it will be *closed* if there is no response 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