-
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: TriStateCheckbox lost margin between label and checkbox #14369
Comments
Hi @jpgoelz I did a PR solving the problem. But I fixed also the examples in the website because were failing. If you use the attribute Thanks for report it! |
Hey, thank you for the fast response! The issue with clicking was regarding clicking the label: of the tri-state-checkbox: I guess my "minimal working example" was too minimal. 😅 |
Yeah, don't worry with my PR will fixed the problem, If PrimeNG Team approve it and it's a good solution for them, will be released. |
Perfect, thanks! |
@cetincakiroglu, this was released in 17.2.0 but does not appear in the Changelog. |
Yes, it does @jpgoelz. |
no problem, happy to help! |
Describe the bug
There is a design bug which was introduced by first replacing
p-checkbox-label
withp-tristatecheckbox-label
in#13977, then just removing the class altogether in #14312 and readding it in #14360.
When checking the changes between 16.6.0 (the version I know where both clicking the label and the style were working correctly) and 17.1.0 (link), I notice that the
p-tristatecheckbox-label
CSS class does no longer exist and should be replaced again withp-checkbox-label
to fix this.Additionally, the on-click event should be re-added to allow clicking on the label.
Environment
n/a
Reproducer
https://stackblitz.com/edit/77z5q5?file=src%2Fapp%2Fdemo%2Ftri-state-checkbox-basic-demo.html
Angular version
16, 17
PrimeNG version
16.9.1, 17.0.0, 17.1.0
Build / Runtime
Angular CLI App
Language
TypeScript
Node version (for AoT issues node --version)
20.x
Browser(s)
No response
Steps to reproduce the behavior
No response
Expected behavior
No response
The text was updated successfully, but these errors were encountered: