Replies: 4 comments 4 replies
-
Yes, whatever CSS is defined last will override any previous rule. Or if there is any more specific selector it can also affect any other rule. That is how CSS works, and why it has cascaded in its name. One possible solution would be to have My advice is to see what exactly is winning on the ABP theme and then try to create a CSS selector that would be much more specific to override it. |
Beta Was this translation helpful? Give feedback.
-
As far as I know, CSS isolation doesn't work with any Blazor component. Only for the native HTML elements. This is not just a Blazorise limitation but for any other component library. The reason is that Blazor must generate inline styles on compile-time, and component libraries are already compiled. |
Beta Was this translation helpful? Give feedback.
-
It shouldn't need to be that hard. Just a little more code than usual. You can start by adding a custom class name to the <Card Class="my-custom-card"> and then some CSS .card.my-custom-card
{
box-shadow: 0px !important;
} |
Beta Was this translation helpful? Give feedback.
-
CSS isolation, cannot work for the Blazor component because on compile-time Blazor needs to generate a special ID on the HTML element that looks like You could make it work by wrapping the component with the |
Beta Was this translation helpful? Give feedback.
-
I commented on this issue where adding
Shadow="Shadow.None"
to a Card in abp.io doesn't take affect.Is that just how it is supposed to work? I would think adding
Shadow="Shadow.None"
right onto the component would override all others styles but is the theme applied last?Beta Was this translation helpful? Give feedback.
All reactions