-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Menu componets: Design Token does not work #6129
Comments
The same situation also has: popover, menu |
I think it is because of the of Menu.vue. <Portal :appendTo="appendTo" :disabled="!popup"> (line2 in Menu.vue). |
I think it because of the Portal is outside of the div.. it iwll influence all components with that: |
Running into the same problem here. Something of note, the problem only occurs when using a scoped design token. I can set the style using design tokens in my global component preset theme. However that isn't what I want to do, I want to use a scoped token to only style a specific menu and not all of them. This is only primevue 4.0.4. |
That’s right and i think it just because of the If you remove them from Menu.vue and the dt will work |
Is this the same matter also for the Dialog component? |
Thanks for the reports. It'll be fixed for version 4.0.6. |
Oh this is a bug.. |
@tugcekucukoglu Tooltip still doesn't react on changes of Design Tokens property. |
Button and Tabs Also don't seem to work. |
The select component is valid here before, but it is not valid today |
Thanks for the stackblitz examples. We are investigating the issue, which will be fixed for the next version 4.1.0. |
Describe the bug
Design token do not work on MENU, these is no 'PC{id}' in the
Reproducer
https://stackblitz.com/edit/primevue-4-vite-issue-template-fhzqdg?file=src%2FApp.vue
PrimeVue version
4.0.1
Vue version
4.x
Language
TypeScript
Build / Runtime
Vue CLI App
Browser(s)
No response
Steps to reproduce the behavior
Just like the case demonstrating.
does not workExpected behavior
I think there must be some code missing....
The text was updated successfully, but these errors were encountered: