The most common use case for components is creating “master” component for list item, blog post etc, and then creating 4-5 instances with changed text for creating a listing.
Changing style of the “master” component should’t require reseting all the text changes done to the instances. It defeats the purpose for using components as a way to decrease the repetitive work.
Please change this logic
For me it seems to work properly. If i change the style of the master, the text in the child remain the “modified” one.
I think it’s the same issue as this Component overides
Penpot team said they were looking into it.
For me everything work as expected (short video). Maybe the problem has been solved or occurs in particular situations/conditions.
Try changing the text color or font on the component, it will not propagate to the modified instance like the other properties.
Ok, the problem only occurs for text styles (font and font color) in instances where the text has been changed. For color, using tokens solves the problem; for font change, not yet…
Unfortunately you have to be super precise with using tokens and never click on the other coloring option because it can trigger the problems written above.
I think there should be following options in the component:
Also changing text shouldn’t “detach” component style from the “master/main”
I agree with you on everything, but I guess being super precise is an essential part of our job!
We should be precise with the designs. Tools themselves should forgive us any mistakes.
