I appreciate the quick reply. However, for business planning purposes, simply waiting for news is unfortunately no longer a viable option for me.
My ability to provide accurate timelines to my own clients is directly impacted by this unresolved issue. This is not just a styling concern, it is a components concern in general; it affects core project architecture and my professional credibility.
To make critical decisions for my current and future projects, I urgently need a clear and official position from the Bricks team. An estimated timeframe, a public roadmap, or even a target quarter for the fix would be sufficient.
Without this information, I am forced to begin evaluating alternative builders to ensure I can meet my commitments. I hope we can avoid that.
I would like to think that you guys are really busy because is the end of the year. But also, I cannot let go an idea passing through my mind that in the end you guys are in the same pocket as the other companies which create softwares/themes/plugins for this community.
So, I will try one more time:
Could you please provide an estimated timeframe, a public roadmap, or even a target quarter for the fix?
Apologies for the lack of a follow-up response. I only just saw your Facebook post.
To give you an update: we do not provide timelines for bug fixes. In practice, they are not reliable to predict, especially if it’s a tricky CSS specificity issue that may affect existing sites. As you saw in the thread, we did implement a fix for this issue, but during testing it introduced other problems that affected more existing setups than the original issue would solve. Because of that, the fix had to be reverted.
This is one of those cases where the problem itself is relatively narrow, but any change to selector specificity at the Theme Styles level has wide impact. We want to avoid shipping something that breaks existing sites, even if it resolves this specific case. So hopefully we can land at such a solution.
Based on your comments, I am assuming you already have a custom CSS workaround in place. If that assumption is wrong, I can share a concrete workaround you can use in the meantime while we look for a proper solution.