Browser: Chrome 110 OS: macOS / Windows / Linux / etc. URL: Link to a page that illustrates this issue Video: Short screen recording that illustrates this issue (free tool: jam.dev)
[Please describe this bug in as much detail as possible so we can replicate & debug this bug]
Hello!
Nested component properties don’t seem to work when set to the Global Classes type. Selecting an override from the parent / root level doesn’t override the global class on the nested element, which remains ‘stuck’ on the default.
Thanks for your speedy response. I’ve shot a screenshare to show you the issue I’m facing; I’m now using the stable 2.2 version.
– Overriding component properties of nested components from a parent component doesn’t seem to work. I’m only experiencing this issue when the component property is a Global Class type. It looks like it’s removing the global class completely when I toggle a nested component’s property from the parent level.
– Updating component properties of nested components while editing a parent component sometimes doesn’t show updates in the Bricks Builder, only on the live site.
Now I can reproduce the problem and have created a task for it.
If you open the developer tools and examine the button after selecting a class in the parent component, you should be able to see that the class is not added at all (on the canvas). At least, that’s what I can see in my simplified component.
However, it is questionable why your primary button suddenly adopts the default primary styles—I don’t have an explanation for that yet, and I can’t replicate it
Thanks Timmse — my theory around the button reverting to Bricks default, is that somehow the bug is stripping the component of any Global Class at all, when toggling a nested component from the parent level. And since my button component requires my custom Global Class (brxe-button-primary) for custom styling, once this is stripped out, it reverts to default Bricks styling?