Community forum for knowledge and support

Updated 3 months ago

Calling Out an Issue with the Global CSS Set Up on the Clonable

At a glance

A community member is experiencing an issue with the global CSS setup on a clonable, where certain Webflow CSS classes are interfering with the ability to style the nav link classes on a nav component. The community member is unable to override the color, font, and text decoration of the nav links due to the attached CSS. Another community member, Matt, responds that they have been identifying similar issues and suggests deleting the body * {} and a, declarations from the global styles embed, as it won't cause any harm. Matt also mentions that an update to address this issue will be released in a new style guide update in the coming weeks.

Guys, calling out an issue with the global css set up on the clonable.

In this case, I am calling out the inheritances set up on certain webflow css classes that get in the way of being able to work with the classes of certain components.

Now, for example, I am trying to edit the nav link classes on a nav component and color, font and text decoration becomes impossible to style via the class or the All links directive because if the attached css.

So I just wonder, what's the point of having this if the classes won't supersede (obviously) because the classes specified in the image get appended to elements after the ones set by us i.e: navbar8_link w-nav-link

Do tell me if I am missing something here. This is from a freshly cloned style guide/site

Attachment
Screenshot 2025-02-10 at 3.17.42 PM.png
M
D
3 comments

@Diego Gallovich we have been identifying some issues around this, and the one you point out being one of them.

Feel free to delete the body * {} and the a, declarations from this global styles embed, it won't hurt anything.

We'll have an update to this in a new style guide update releasing in the coming weeks.

Add a reply
Sign up and join the conversation on Slack