Changelog

Makes the CSS editor in Bricks a workable height and moves some rarely used fields that were positioned before it, to a position below it.

Moves the CSS tab in Bricks to the top of the list on the styling panel for users who prioritize custom CSS over segregated styling inputs.

New border mixin for adding global border styles.

New .is-bg utility for instantly turning anything into a background.

The simplest and easiest way to create inverted border radii in the world of CSS.

Fluent Forms and WS Forms enhancement only.

Read details.

Read details.

This is a potential breaking change for custom card styles (but not likely).

“Exclude ‘.btn–‘ Selectors input added to Buttons > Options > Additional Options can be used to programmatically block default button styling from selected elements. Very useful if ACSS is affecting styling of 3rd party buttons.

You can now use classes with a double dash in exclusions without triggering var() wrapping.

A few utilities were getting removed incorrectly. This feature is still experimental and is waiting on expanded logic to cover all scenarios, but this fix will still improve things short term for at least one known user who experienced issues.

ACF was having its font size manipulated by ACSS resulting in large fonts in certain ACF fields. This is fixed.

The logic for populating Bricks’ dropdown with available button styles needed improvement for existing ACSS sites. Previously enabled/disabled buttons would sometimes show in the dropdown as available options when not currently enabled. We’ve added a reset for checking the currently available styles on upgrade.

You can now use the Bricks button styles UI to apply button style classes to buttons. This feature must be enabled in the Bricks Enhancements area of the dashboard.

You can now control default button size for cards.

Classes like .service-card-group were triggering the card framework. Much like “wrapper,” “group” is now an anti-keyword.

Clicking an element that has hover focus no longer shows the focus styling. This makes for a cleaner user experience.

Headings would be 700 either way, based on browser default, but some users wanted it to show 700 as the value in the dashboard for added clarity.

The context menus have now been updated to include all contextual shades and transparencies.

We now only strip var() instances when there’s a single variable in use. For more complex scenarios, we leave the vars intact. You don’t have to write var() as we’ll add it for you automatically, but we won’t visually strip them if there’s more than one.

We’ve updated the context menus to support dark/light button variants.

In rare situations, font families need to be wrapped in quotes (e.g. “Source Sans 3”), but our parser was stripping quotes. This is now fixed.

Clashing JS variables caused the dashboard not to load when setting the ACSS_FLAG_LOAD_DASHBOARD_SCRIPTS_AS_MODULE flag to false. This is fixed.

This was found during internal testing and wasn’t yet reported by users. The background position property wasn’t being output for textures 2 through 5. This is now fixed.

Disabled transparencies were showing placeholder swatches in Gutenberg color palettes. This is now fixed.

Existing color palettes by Gutenberg or third party tools were still remaining. This is now fixed.

This is a partial fix that demands a little bit of refactoring in January. The issue stems from processing mixins and functions. It occurs very rarely, but will be addressed further in January.