Changelog

• 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.

Heading and text font family support. These values no longer need to be added in the builder theme styles.

You can now control alignment on buttons, an improvement on the previous “center” default.

This was a loop issue. Added a conditional to handle .width--full independently.

A typo in the logic statement was causing deprecated section padding classes to not load when the toggle is on.

Some users were using the deprecated “doorway” file via third party SCSS plugins. We’ve restored this just so these users don’t have to swap out the path for automatic-imports.

Users can now change link hover styles on the fly for individual links or groups of links with .link-hover-- classes.

.btn--none prevents auto .btn-- syntax matching in case users want to use the .btn-- syntax, but don’t want ACSS to apply global button styles automatically. It also clears user agent styling on <button> elements.

• Stack elements panel (single column)
• Remove walled-garden elements (“builder pro mode”)
• Remove redundant components (for Frames users)

The builder will now remember its open/close position separately on the frontend and backend. For users that don’t open the dashboard on the front end, this will keep the dashboard closed on the frontend even when you’ve left it open on the backend.

These features were improved for consistency and code efficiency.

When setting sections to default to content grid structure, users now have programmatic control over where that structure is excluded. For example, you can exclude third party code that uses <section> elements from having their structure changed.

We no longer use wp_environment_type for development as this was creating conflicts on some dev installs.

This was automatic in the past, but it now has a toggle in case users want to disconnect header height from scroll offsets.

No more relying on the keyboard shortcut or clearing searches in order to save.

Some random toggles suggested the current value was not the default when it actually was.

Gutenberg is a real joy to work with.

Not all global styles were being applied from the dashboard to text sizes when using text size classes. This is fixed.

If your Gutenberg instance uses the non-iframe version of Gutenberg, you’ll see proper spacing now, assuming you’ve turned off “Use Gutenberg for Page Building.”

This toggle works now.

Pasting a value in the box-shadow input sometimes resulted in a value of “0.” This is now fixed.

• Fixed progress bar styling
• Fixed font size styling

• Fixed a bug causing invalid input text color visibility issues with dark form styles
• Fixed active tab border style conflict with step numbers

Size would compute to “0px” when the input was blank.

Boxed layout was throwing the dashboard off the screen.

Searching in the cheatsheet was producing a second save button near the search input that isn’t needed. This is fixed.

You’d need to refresh on earlier versions. You no longer have to do this.