When building Nested Components, it is possible to link Global classes Property from a nested component to the parent Global classes Property. But unlike other properties, the Global classes Property is not working when using the parent component instance.
I built these Global classes properties exactly the same (same options, same labels, same css classes). I tried out the Select Property and this works fine.
Since this is a bit complex, here are the steps to reproduce it:
Create a Block with an icon and text.
Select the icon, create a class and set an icon color. Repeat for a second class with different color. Remove both created classes from the icon.
Select Block and make component (child).
Create Global classes property with the two created classes. Assign the property to the icon class.
Leave component. Make new Block, add the previously created component as instance and make the new block a component (parent).
Create Global classes property with the two created classes. The Values need to be identical to the previously created property.
Assign it to the child instance property within the parent component.
Leave component. Change parent instance property.
Hi @davidfrx,
Thank you for reporting this issue with detailed steps 
I have added this to our internal bug tracker.
We fixed this issue in Bricks 2.2 RC, now available as a manual download in your account (see changelog).
Please let us know if you are still experiencing issues.
As with any pre-stable release, please do not use it on a production website. It is intended for testing in a local or staging environment only.
Hey @timmse, I am running the 2.2 RC version and still experiencing this issue. @davidfrx Did the update fix it for you? Thanks!
Hi @robert_looplabs, I can’t replicate the issue in our latest 2.2-rc2 version. Can you share more about how the components are set up on your end?
Hey @robert_looplabs ,
It would be really great if you could provide us with your components!
We have a similar report here where I can reproduce the problem, but without your components, we can’t know for sure if it’s the same problem.
Hei @timmse, hey @robert_looplabs
I quickly checked this when RC1 came out and thought it works fine. But now I started a project with 2.2 and the global classes property bindings seem not to work. Not 100% sure if it was fixed previously or if I just didn’t check properly.
The video should explain a bit what issues I’ve found:
Component JSON:
Thanks so much for the video @davidfrx !
I just searched our tasks again and found one that sounds pretty much the same, which has been reported by email.
I added your report to it, and we’ll update this thread once it has been fixed.
