No. When YOU set the styles, it goes by what you set. So if you add a heading element or a paragraph element and want to change the max-width to 30ch, you go to the element and add the max-width, and it works fine. If you prefer to use a code-snippets plugin, you can use the method Thomas noted earlier; it’s a more specific rule so it overrides the defaults.
This was in reply to Kevin’s question above me, not the OP.
Edited for clarity: you could also create your own class in the builder or out that sets the max-width. You have options. The OP is referring to his options with the framework targeting. It’s different than you as the individual using Bricks Builder styling, classes, or a code snippets plugin; you have complete control.
This is a bug! How can it be marked “No Bug”. If a standard CSS framework like ACSS has no practical way of overriding this attribute selector, then it’s a bug in my opinion. It’s not like this selector was always there - it was recently introduced. So clearly it’s not 100% needed for Bricks to work, even if it is useful in many cases.
Regardless, setting [class*=“brxe-”] { max-width: 100%; } for everyone with no way of turning it off is causing a lot of headaches, especially the for the biggest fans of Bricks Builder (ACSS users).
It is also used in various other places throughout Bricks source code for selectors so also unsure why it would not be added to the [class*="brxe-"] as stated in the OP thread and solve this issue.
body{max-width:100%} just applies to the tag alone. Anything inside the body does not inherit this.
[class*="brxe-"]{max-width: 100%} applies to every element which has a class beginning with “brxe-” which is pretty much every element bricks adds to the DOM.
This makes every single element have a max-width of 100% which is where the OP bug stems from.
Using :where() selector solves this but it seems the Bricks team are unwilling to implement or talk further about it. No real response outside of @thomas original “NO BUG” and add this a “feature request” comment.
Edit: I just checked bricksbuilder.io and its obviously built with Bricks, but it doesnt even have the [class*="brxe-"]{max-width: 100%}… it seems like there is a special version of Bricks
@thomas@timmse@aslotta@charaf would any of you guys be able to update us on this thread and why there has been no further conversation about the use of :where or @layers for Bricks default styles.
Please reconsider addressing this issue again to improve the usability and flexibility of Bricks. We do need this fixed; This shouldn’t be a problem we are facing in an awesome builder like bricks anyway.
It’s been almost a year since this was initially discussed and sadly there isn’t a solution, yet. Is this still under consideration? It would be great if you can give some love to this issue!
It won’t get the upvotes for visibility. Need more back to top buttons and section dividers first!!
If the devs wanted to do something about it they would have done by now or at least voiced they are looking into it. Once it gets assigned NO BUG it gets ignored.
I have accepted that I will to work around it and it will just be “one of those things”
Perhaps @Matej might be able to ping everyone again for a review.
