That statement contradicts how cascade layers are meant to be used. The entire point of placing default styles in a lower-priority layer is to make them easy to override .
If you define styles in the Bricks UI, they shouldn’t be in the layer because they shouldn’t be overwritten.
The layer should only contain resets and defaults, such as brxe max-width: 100%, but not styles that are changed/adjusted in the Bricks UI.
Why does this styling for example have to be in the layer?
Independent of ACSS. The class name .sticky is far too general. Any user could create a .sticky class and thus override this styling in the header, right?
And the same goes for the Masonry Gallery.
The only thing outside the layer is the variable “var(–gutter)” which overwrites the value in the Layer.
Regardless of whether it’s set to the ID or the class in the Bricks UI. It’s only overwritten as a local variable, but that doesn’t prevent this styling from being overwritten by another stylesheet.