-
Notifications
You must be signed in to change notification settings - Fork 4.5k
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
Calendar: Calendar CSS breaks other Components #14606
Comments
+1. In case of |
Indeed, upgrading from 17.3.2 to 17.3.3 introduced, in our case, a bug for this case: With these 3 attributes combined, and @denny99 Are you sure that even with your fix, the calendar icon, when inside the input component ( |
When clicking the icon inside the input. The click will pass through the icon itself. So you actually click the input and this opens the input on focus. So yeah. When you disable the open on focus this won't work at all. I guess the design team has to find another solution for this one. The original bug report that caused all this trouble was this one here #14501 |
Yes, but shouldn't it be simply reverted, until, as you're saying, the design team finds another solution? |
I'll change the pr later |
@k0sr Thanks for pointing out the potential bug with showOnFocus. The new fix should, at least partially, solve both issues. |
Hi, Thanks a lot for reporting the issue and the PR! |
fix #14606 restricted pointer events more
Describe the bug
The Calendar CSS breaks all other Components that use icon wrapper and click Events. Like the p-chips Component
Environment
Does not matter
Reproducer
https://stackblitz.com/edit/github-sstt7q?file=src%2Fapp%2Fapp.component.html
Angular version
17.1.0
PrimeNG version
17.3.3
Build / Runtime
Angular CLI App
Language
TypeScript
Node version (for AoT issues node --version)
v20
Browser(s)
No response
Steps to reproduce the behavior
Just enter something into the chips element.
Try to remove the chip with the times icon.
Not working due to the calendar css
Expected behavior
No response
The text was updated successfully, but these errors were encountered: