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
Despite the Aura theme having the following for outlined buttons:
button: {
colorScheme: {
light: {
outlined: {
contrast: {
borderColor: 'orange', // <- Works
activeColor: 'red', // <- Does not work
},
},
},
},
},
Changes to the activeColor have no affect, and are not defined in the css so far as I can tell.
This not the first broken token I've come across while styling v4 while upgrading from v3, which is the reason I'm finally creating a Github issue for it now. It's been quite frustrating, and really makes me miss working with plain CSS for styling. However I can definitely see the pros of working with this kind of system, so I've been pushing through with css hacks to make things work the way we need it to.
Is this something I should be keeping track as I go (the broken non-affective tokens)? Is there a centralized place where people should be reporting these? Any chance someone could be tasked at primevue with going across all the tokens to make sure they work?
We're unable to replicate your issue, if you are able to create a reproducer by using PrimeVue Issue Template or add details please edit this issue. This issue will be closed if no activities in 20 days.
The original question remains however, I've come across many of broken tokens styling v4 (at least 4 so far). Should I be keeping track of all them and creating separate issues for each?
Describe the bug
Despite the Aura theme having the following for outlined buttons:
Changes to the activeColor have no affect, and are not defined in the css so far as I can tell.
This not the first broken token I've come across while styling v4 while upgrading from v3, which is the reason I'm finally creating a Github issue for it now. It's been quite frustrating, and really makes me miss working with plain CSS for styling. However I can definitely see the pros of working with this kind of system, so I've been pushing through with css hacks to make things work the way we need it to.
Is this something I should be keeping track as I go (the broken non-affective tokens)? Is there a centralized place where people should be reporting these? Any chance someone could be tasked at primevue with going across all the tokens to make sure they work?
Pull Request Link
n/a
Reason for not contributing a PR
Other Reason
No response
Reproducer
https://stackblitz.com/edit/primevue-4-vite-issue-template-raglweh5?file=src%2Fmain.js
Environment
n/a
Vue version
3.5.12
PrimeVue version
4.2.5
Node version
No response
Browser(s)
No response
Steps to reproduce the behavior
Install the latest Primevue v4
Optional: Latest Apollo Theme
Expected behavior
All currently implemented component tokens be functional and defined in the CSS.
The text was updated successfully, but these errors were encountered: