Changelog

Users can now choose to use global button styles for form buttons instead of managing form button styles separately. Each type of form button can have a global button style assigned to it. Supports all button styles including outline variants.

Since Smart Spacing only applies to top level elements, multi-paragraph blockquotes were not getting Smart Spacing applied. We’ve enhanced SS to include blockquotes.

In some uses of Auto Grid, items were stacking too soon. Not only have we fixed this, we’ve provided a new control so users can dial in the exact aggressiveness they want in their Auto Grids. This control is called “Aggressiveness” and it’s found in Layout > Auto Grid. And don’t worry, this is just for the default and can easily be overridden at the instance-level.

It was working in live preview, but wouldn’t commit new values to the database. This is fixed now.

• Menu dropdowns were getting contained inside the header and clipped. This is now fixed.

A bug was causing radius size variables to not load even when the “Generate Extra Radius” sizes toggle was on. This is fixed.

We’ve brought significant improvements to auto-grid functionality while maintaining backward compatibility with existing auto grids. Full details on auto-grid here.

Note: Logic for showing/hiding Auto Grid classes based on the new Auto Grid option switch will be added in a future update. We didn’t want these new Auto Grid improvements to wait on inconsequential context menu logic.

The utility classes area under options now has a toggle that allows you to switch off all utility classes at once. You can still toggle individual utility modules one by one as well.

The stretch class was setting display to flex. In most cases this isn’t a problem, but it’s also unnecessary and potentially conflicts with the use of this class in certain grid scenarios. We’ve removed the display property.

Turning off “additional radius sizes” would previously deactivate useful radius classes like .radius--50, .radius--circle, and .radius--none. This is no longer the case. You can turn off the sizes without affecting these classes.

Bricks v1.10 brings changes to the template gallery in the form of masonry layouts. Our previous optimizations would break this new layout structure, so we’ve made changes to prepare for the full release of 1.10.

Light/dark button variants, tertiary button options, and neutral button options are now added to the pre-loader for class auto-suggest. You’ll need to deactivate and activate the plugin for these classes to be added to the builder’s auto-suggest feature.

Placeholder style values weren’t sticking. This is now fixed.

This was a JSON issue. The duplicate line height field is now gone.

• Support for defining explicit grid rows (.grid-row–).
• Span classes can now be used simultaneously with start classes.
• Column span and row span utilities now support up to all 12 columns in context menus.
• Added .grid–auto-rows to context menu.

Note: Not all features have full documentation yet, so links may be missing from some areas.

This was on by default at all times. Some users were confused by how it might affect logos a few other things. This isn’t really a problem for anyone who knows what’s happening, but for new/beginner users it can be confusing. So, auto object fit is now behind a toggle that defaults to off on new installs. You can opt-in if you want auto object fit.

Was outputting --radius--m instead of --radius-m

Up/down arrow cycling in color inputs was working when the value was already a shade, but not when the value was a main color. This works across the board now.

We’ve made a temporary change that will reduce the instances where a user can’t open the dashboard. This change also allows users to work with ACSS without an internet connection.

Gutenberg is a dumpster fire.

Smart spacing can’t know which third party tools you’re using, so you need a way to tell ACSS to apply smart spacing in these areas. That’s easy to do now.

Having these in the context menus makes it easier to apply/follow the new standard for global radius and border styles.

The skip link styling was on the old button code. It’s now up to date with current button styling output.

• Removed action color from datepicker
• Added range slider thumb color control

Transparencies are working, they just weren’t selectable in the context menus. This is fixed.

These were missing from our migration/upgrade conversion list. They’re fixed now.

Our validation code incorrectly identified dashes in certain strings (e.g., font families) as arithmetic operators for the “calc()” function. We’ve temporarily disabled the check for the “-“ sign specifically while we find a definitve fix.

The values for the box-shadow setting were ported correctly, but displayed incorrectly when they contained a “;”. They now display the full contents.

Multiple users have tested 3.0.2 and verified that this fixes their issue. Not every user was experiencing the fatal error, but if you were one of the users experiencing this issue, 3.0.2 should fix it for you.