You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The border-radius for the checkbox component uses the global definition for it ($borderRadius). However, if I look at the theme presets on PrimeVue docs, the value differs when applied to the component.
The problem with this definition is that the checkbox becomes almost round for larger radius values. Still, most importantly, it behaves inconsistently based on what's in the document versus what's generated with the sass themes.
Example of field with the default radius value:
Example of checkbox with the overwritten value:
These specs aren't available on the Figma file either so it's hard to understand what's happening here.
Here's a sample stackblitz project to validate that. The difference can be seen in the below comparison as well:
What's the best approach to solve this issue?
I wouldn't like to custom change the theme as it'd require us to manually update it on every PV or theme update.
The text was updated successfully, but these errors were encountered:
@tugcekucukoglu do you have any feedback on this topic? I could open a PR if that's allowed. The main issue I see is that this property is not available as a token in the UI Kit.
The
border-radius
for the checkbox component uses the global definition for it ($borderRadius
). However, if I look at the theme presets on PrimeVue docs, the value differs when applied to the component.The problem with this definition is that the checkbox becomes almost round for larger radius values. Still, most importantly, it behaves inconsistently based on what's in the document versus what's generated with the sass themes.
Example of field with the default radius value:
Example of checkbox with the overwritten value:
These specs aren't available on the Figma file either so it's hard to understand what's happening here.
Here's a sample stackblitz project to validate that. The difference can be seen in the below comparison as well:
What's the best approach to solve this issue?
I wouldn't like to custom change the theme as it'd require us to manually update it on every PV or theme update.
The text was updated successfully, but these errors were encountered: