I’m also experiencing this since updating to 1.5.3.
When I set a border radius on buttons via theme styles, that radius is not inherited by the actual buttons. Setting a border radius on the button elements themselves does work.
There is also a problem with the Border Width Linking option. It doesn’t work.
Plus the Border width, when set manually in Theme styles, is forgotten once you leave it.
removing .bricks-background-primary will do the trick and your settings from theme styles will be active, just did not find out yet where and why .bricks-background-primary is applied at all when the element has a style in the theme styles.
When we remove the Theme Style Colors, we need to address the buttons anyway. As for the “Default” button, I think it’s a definition issue. As far as I understand it, the default button is currently used when no other button style (Primary, Secondary, etc.) is selected. But that doesn’t mean that e.g. the primary button takes the border-radius from the default button.
As I said - we’ll have to look at it again when the Theme Style Colors are discontinued.
@alanj Which browser are you using? I cannot reproduce the problem. @Claudio Looking forward to your (reproducible) reports
In the Theme Styles? Not at all. This will cause you problems at the latest when the theme style colors are gone. Therefore I would recommend you to work with classes instead, which is the most bulletproof solution, and you have full control over it (now and in the future).
For example (written as regular CSS, but you can easily create these classes with Bicks):
.btn { ... contains general styling as e.g. padding... }
.btn-rounded { ... contains your border-radius... }
.btn-muted { ...contains the muted background-color / color }
.btn-primary { ...contains the primary background-color / color }
I would expect “default” to mean the one that the other styles pull from if they have not been modified in a certain way. In fact that’s how it works for typography I noticed already (so at the very least there’s an inconsistency here which is a defect IMO)…
…if I set default to a typo weight of 800 for example, then all the other button styles immediately get the 800 weight even though it wasn’t specified beyond the default style.
As that behaviour is shown for typography, I’d expect the same behaviour in the border radius as another example, and currently that isn’t happening. This is a defect IMO.
Notice in the screenshot below… I have set the typography in default, but not in primary or secondary, but notice they still have the heavier font weight as specified from default. However that is not the behaviour seen for border-radius (set on default but not set on other styles).
Hopefully it’ll be resolved very soon. Thank you.
@timmse, can we please get an update on this one? Is this not a bug being worked on? I’d expect this to be in WIP rather than WAIT state. If you need a recent detailed explanation of the defect, please review this comment: WAIT: Button Border Radius can not work - #12 by d19dotca
I think you misunderstood the issue (or I’ve misunderstood your screenshot). The border-radius works fine if set explicitly like it looks like it was in your case. However if you set it on “default” only, then it isn’t inherited by the other styles, despite all the other settings being inherited such as typography. This means it doesn’t behave the same way as it doesn’t for the other settings under the default style where the others inherit it, it seems to stick to default only which means the workaround for now is it needs to be set explicitly on every style that needs a radius.
@timmse - Is it possible to get an update on this? This issue has been long-standing. It’s currently set in WAIT status but I’d like to hope this is in the bug backlog and thus WIP status instead. Is this currently waiting on any users input at all or is this with the Bricks team currently for hopefully a fix in the next version or two?