Problems with the New Class Selector

[DesignerDiana (Diana)]

Continuing the discussion from The new class selector:

@vlogic

Renaming a global class is destructive and will break in all cases as the warning in the style manager indicates. This is not a desired behavior / outcome.

Other random behaviors are not present in a new build. I see some additional warnings, so I assume some of this is actively changing.

Continuing the discussion from The new class selector:

@vlogic

I have noticed this also when playing with the new selector. It breaks the association of that instance entirely and starts from scratch wiping all properties. BUT the behavior is not a constant. According to how the order of combo classes are stacked. I am re-testing from a very simple scratch build, because I think I am getting several different outcomes upon renaming:

1. Renaming destroys all properties in the class under some circumstances (a clean wipe).
2. But, renaming does not always affect all instances of that global class.
3. Clones - or same stack order combos inherit the destruction / wiping upon renaming.
4. Any shuffle of the stack order of global combos behave independently (Combo Stack A does not alter Combo Stack B).
5. Editing the name of the original source div I used to create the global promotes proper inheritance behavior.

Deleting my previous comments - not efficient - sorry. I am off to test this from scratch and will post a cleaner test case for each. Please do the same. This is super important to know exactly what is happening and get a clean result and resolution / support for any issues.

Continuing the discussion from Classes bug-uneditable classes:

@Mowgli

I think similar problems have been mentioned before. Basically I have certain classes that I can’t edit.
As you can see below there’s a class called “login button” which doesn’t appear in the class selector. Very frustrating!

Attention Webflow staff members,

Was wondering if there are any updates on the above issues with the class selectors, found by us webflow lovers?

Along with the above bugs stated by @vlogic and @Mowgli, I have also been experiencing with removing nested classes and joint global classes from elements. After asking on the forum I found out that this issue is due to classes being defined twice on one element automatically by webflow class selector.
So when an element has more than one defined class and you wish to remove the outermost child class … it is not possible because it has also been defined as a parent class. Meaning that, not only that you can’t remove the child class you can’t remove all the other classes above it because currently webflow class selector only allows users to remove classes from a element in order.

Anyhow there is a solution, that is if you rename the child class … it is then removable but the class will no longer have any css properties associated with it and all other elements that uses that class will change because the class name is no longer the same as the global class name that the class has inherited from.

At first the solution worked okay for me since it only made me use a bit more time. But after a while this becomes a big issue because all my classes become unstable and messy due to all the renaming. Therefore the designing process in webflow now, has become more tedious, frustrating, annoying and time consuming. I had to spend hours figuring out what class I just renamed that caused some elements to misbehave … next and I go and fix it, hoping all will work out just to discover that another class needs renaming.

At one point I gave up and headed to the backup page to restore my project … which I came to discover that the preview button has been taken off. Therefore I didn’t want to take the risk of not knowing what I would be restoring my site to, so I went back to dealing with the disastrous class selector.

The button is also another issue, please acknowledge.

Cheers,

Diana