Skip to content

Changing Shadow Classes on Popover and SelectMenu #3874

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

Open
saschafuchs opened this issue Apr 13, 2025 · 0 comments
Open

Changing Shadow Classes on Popover and SelectMenu #3874

saschafuchs opened this issue Apr 13, 2025 · 0 comments
Labels
question Further information is requested v3 #1289

Comments

@saschafuchs
Copy link

saschafuchs commented Apr 13, 2025

I currently have the problem that we have to integrate our SPA into a larger application. And with that, we also inherit the CSS of the outer application. And that's where it gets really ugly: they have partially written classes in their own CSS files that use the TW naming scheme (m, p, gap, shadow, etc.), and then add !important to these declarations.

One of the big problems with Nuxt UI is that there is no prefixing of Tailwind classes. So we started writing TW utilities with a prefix for the affected classes. This is then transferred to app.config. The second problem was the merge process that app.config uses. Usually the names have to match. If I want to have a p-4 from the config (because px values with !important were entered in the outer CSS), I created the class p-00, which replaces the p-4 class and thus clears the way for the prefixed TW class o-p-4.

So far so good, but I can't use it with popovers like SelectMenu. No matter what I do, the class shadow-lg remains. The other devs of the main application have entered a rather ugly shadow with important there.

Is there another prop like 'content' that I can use to replace shadow-lg? I'm not a fan of !important, but at this point I can only work this way.

Furthermore, it would be really nice if you could really overwrite the sections in app.config instead of just merging them (apart from prefixing the TW classes). There are certain stylings that you won't use, but then they are in the element

@saschafuchs saschafuchs added question Further information is requested v3 #1289 labels Apr 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested v3 #1289
Projects
None yet
Development

No branches or pull requests

1 participant