ah. yea. you can do that yet. BUT! what you can do is create a parent class that has the common styles. Then for each new element, give those the parent class name, then put a child class with its own custom styles =)
This would still be a very useful feature for creating varying versions of a design.
The parent class with child classes doesn’t quite work well without creating a lot of messy styles in the end.
An ideal workflow could look like this…
Current homepage design is version #1 (want to keep it untouched)
I make a duplicate of that page to make version #2 (now if I want to change colors, styles I have to give a child class based on my design version rather than semantic elements, adding ultimately useless style names that will have to be purged on export.)
I “save-as” those styles from #1 but can freely explore new variations without affecting my version #1
This is something I’ve constantly struggled with in Webflow and wanted to revive this topic.
If I could capture all the style elements of this button (nested, secondary, everything) and make a new, independent style (think flattened, rasterized layer in photoshop), that would allow me to pivot easier and try out new variations of a style without manually recreating all of those style factors to keep the style manager clean and semantic.
Flattening this and naming it anew would do wonders for productivity for the short and long term.
@PixelGeek Has this issue been made a development item? or has it/will it be reviewed internally again as it’s been year?
The word-around you offered doesn’t work when using interactions (at least not in the particular case I just built).
Copying styles would be helpful, and seems like a fairly trivial dev item.