It’s problematic that every pseudo element / advanced selector you create shows up on every element in Bricks from that point forward.
This makes advanced selectors really janky and unorganized.
Sometimes I need a :nth-of-type(2n + 3) type situation on an element and I’ll never need it again, so why should it show up on every element as an option going forward?
It’s even worse when you try to target child elements of another element with a compound selector. There’s zero use case for that compound selector on any other element, yet, there they are in the list at all times, on all elements.
Hi Kevin,
Thank you for your contribution. This is not a bug but rather an improvement.
Since your request is not a small change, we would be happy if you submit it as an official request: Ideas – Bricks
can i ask why such improvements need a feature request? it’s very obvious that this needs a fix. looking forward to hear and understand why this needs an extra request. thanks!
I dont want to speak on behalf of Stefan, but it’s not a feature request, but an improvement request that Stefan is asking for. The op just stated something they do not like with a current feature with no possible solution of how they would like to see it improved. An improvement request could be compiled with the feedback he received in the FB post
To be fair, it’s not really obvious that this feature needs to be improved. This is the first post I have seen a post about it, and class-based styling was introduced on Nov 21 (10 months). If it was something obvious, I would imagine this to have been raised a countless amount of times.
