-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Component: Autocomplete #14806
Comments
Hi, Could you please share a stackblitz example so we can identify the issue? |
…e end of the panel.
Hi, Since you're using templating, you need to style elements inside the template option. We cannot interfere the styling of user templates. The reason why it stays on top is because the suggestions array empty and there isn't a CSS rule doing it. Here is the refactored version of your example: https://stackblitz.com/edit/bqllri-x2bzc2?file=src%2Fapp%2Fdemo%2Fautocomplete-virtual-scroll-demo.html,src%2Fapp%2Fdemo%2Fautocomplete-virtual-scroll-demo.ts Closing the issue since it should be styled by the user. |
Until version 16 when we used pTemplate="footer", the template was positioned by default, pined, below the scroll bar, in the lazyLoadgin option. Just like the pTemplate="header" is pined above the scroll bar. pTemplate="footer" (lazyLoading option) pTemplate="header" Version 16.2.0 |
Hi @jafidelis , Could you please update the links, they are broken and lead to the github/issues |
fix #14806 Fixed issue of the footer not being fixed to the end of t…
Describe the bug
Autocomplete, footer is not staying in place waiting, staying on top of the first item in the panel list.
Environment
win-11 - WSL
Reproducer
No response
Angular version
17.0.5
PrimeNG version
17.6.0
Build / Runtime
Angular CLI App
Language
TypeScript
Node version (for AoT issues node --version)
18.17.1
Browser(s)
Chrome 121
Steps to reproduce the behavior
Add
<ng-template pTemplate="footer">content</ng-template>
, in autocomplete component.Expected behavior
Pin to the end of the results list
The text was updated successfully, but these errors were encountered: