-
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
Menubar: autoDisplay and autoHide broken #13512
Comments
Hi @g1thuser, they know about the problem and will fix it. The link is this: #13455 (comment) |
Still causing issues on primeng 17.2.0. Steps to reproduce:
|
Still happening on 17.5
Still happening on 17.5, following the same steps described above. Workaround: Define a viewChild for the menu bar and add a mouseleave callback to it and force close, using renderer2:
|
Autodisplay works if change source code. --- a/src/app/components/tieredmenu/tieredmenu.ts
+++ b/src/app/components/tieredmenu/tieredmenu.ts
@@ -695,6 +695,9 @@
onItemMouseEnter(event: any) {
if (!DomHandler.isTouchDevice()) {
+ if (this.autoDisplay) {
+ this.dirty = true;
+ }
if (this.dirty) {
this.onItemChange(event);
}
|
Are there any updates or workarounds for autoDisplay? Still happening on 17.14.1 Found out that its not working only for chrome |
You can do with the tieredmenu component what I did with the fileupload component (#15212 (comment)) and fix it as I mentioned here: #13512 (comment). |
@kubedan Thanks for answer. So theres no solution without updating the primeng code ? |
Unfortunately, I don't know of any other solution. |
Unfortunately, I still have the issue for autoDisplay and autohide. It still not work with v17.18.9. I'm using Chrome. Any solution please ? |
Describe the bug
The autoDisplay and autoHide properties don't work anymore. autoHide doesn't work at all, autoDisplay works only once after clicking on any root menu item. Clicking on a menu item leaves the last clicked root menu item in the selected status.
The error is already present in primeng 16.1.0, but didn't exist in primeng 16.0.2
Environment
Ubuntu 22.04
Firefox 116.03
Reproducer
No response
Angular version
16.2.0
PrimeNG version
16.2.0
Build / Runtime
Angular CLI App
Language
TypeScript
Node version (for AoT issues node --version)
20.5.1
Browser(s)
No response
Steps to reproduce the behavior
see here for primeng 16.1.0
see here for primeng 16.2.0
Expected behavior
see here for primeng 16.0.2
The text was updated successfully, but these errors were encountered: