Remove Deactivated Classes from Database (Bricks)
This new feature is found under Options > Experimental. It removes classes from the database when they’re deactivated in ACSS. This is a performance enhancement to make Bricks snappier and clean up the Bricks classes database.
Two caveats:
Users will need to reload Bricks to see the classes / palettes updated.
The system won’t remove ACSS classes that users added manually because the class IDs are unknown to us. If you added an ACSS class manually because it was missing at some point, we won’t have control over those manually-added classes.
There is still room for granular improvement here (e.g. active/inactive color logic for certain modules), so we’ll continue improving this over subsequent releases.
This is an experimental feature. Please make sure you have a backup before you try it, and let us know if you run into any issues.
Added "Aggressiveness" Control for Auto Grids
This new control allows users to fine-tune the default aggressiveness of element stacking in Auto Grids.
Resolved conflict with Interactive Cursor Elements
Bricks Extras users and Bricks Score users reported a conflict with their interactive cursor element. This should be resolved now.
Updated Auto Grid @recipe
The @auto-grid recipe was out of sync with latest changes to Auto Grid. It’s now up to date again.
Port "Lock Specific Selectors" value on upgrade
This option for color scheme was not being ported properly on upgrades from 2.x. This is now fixed.
"Add radius automatically" is no longer on by default on upgrades from 2.x.
Self explanatory.
Deprecated warnings on update
- 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.
Fixed an issue with dropdown menus in boxed layout headers
- Menu dropdowns were getting contained inside the header and clipped. This is now fixed.
Refactored Auto-Grid Classes
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.
"Classless Workflow" Option
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.
Stretch (.stretch) class improvements
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.
Improvements to radius class loading logic
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.
Compatibility with Bricks Template Gallery in Bricks v1.10
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.
Added new button variants to pre-loader
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.
Fixed WS Form placeholder styling not saving
Placeholder style values weren’t sticking. This is now fixed.
Removed duplicate line height field under H4
Grid Utility Class Enhancements
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.
Fixed documentation links in dashboard cheat sheet
Note: Not all features have full documentation yet, so links may be missing from some areas.
Auto object fit is now behind a toggle (default: off)
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.
Fixed double dash syntax error in radius classes in context menus
Was outputting --radius--m instead of --radius-m
Fixed a local storage error related to dashboard state
Fixed up/down arrow cycling with main colors
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.
Change to reduce "dashboard won't open" issues.
Increased .smart-spacing specificity to override Gutenberg more consistently
Gutenberg is a dumpster fire.
Added input for applying smart spacing programmatically to 3rd party areas
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.
Added new global radius and border vars to context menus
Having these in the context menus makes it easier to apply/follow the new standard for global radius and border styles.
Skip link now matches button styling
The skip link styling was on the old button code. It’s now up to date with current button styling output.
WS Form Fixes
Removed action color from datepicker
Added range slider thumb color control
Fixed neutral transparencies not showing up in context menus
Transparencies are working, they just weren’t selectable in the context menus. This is fixed.
Fixed an upgrade/migration issue with semantic shades (medium/ultra-light/ultra-dark)
These were missing from our migration/upgrade conversion list. They’re fixed now.
Fixed validation that was messing with font-family input
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.
Fix box-shadow values not displaying the full contents when containing a ";"
Support for font family
Heading and text font family support. These values no longer need to be added in the builder theme styles.
Justify and text-align controls for buttons
You can now control alignment on buttons, an improvement on the previous “center” default.
.width--full is no longer based on content width
This was a loop issue. Added a conditional to handle .width--full independently.
Fixed logic for deprecated section padding classes
A typo in the logic statement was causing deprecated section padding classes to not load when the toggle is on.
Restored the "doorway" file for backward compatibility with 3rd party SCSS plugins
This is our standard post-release update focusing exclusively on bug fixes and improvements.
Programmatic color scheme protection
Documentation: https://automaticcss.com/docs/color-scheme-dark-mode/#protection
Gutenberg styles no longer load in the preview area when "load styling in backend" is disabled
Auto-BEM no longer disrupts Bricks global classes
Section spacing is now visible in the context menu on spacing inputs
Compatibility issues between contextual color utilities and color scheme protection classes are now solved
Compatibility issues with color scheme protection classes for website background color, text color, and heading colors have been fixed
Relative paths in import statements no longer cause issues with SG Optimizer
Headings now switch colors automatically when using auto color relationships
This is a security release that fixes a potential XSS and CSRF vulnerability in our backend. The update won’t impact the layout and styling of your websites, so you can perform it safely.
This is our standard post-release update focusing exclusively on bug fixes and improvements.
Content-grid class now has the correct specificity
This fixes the bug reported in [RESOLVED] Content Grid not working – am I missing something? | Automatic.css (automaticcss.com)
Heading colors now apply the correct value
This fixes the bugs reported in:
Bug Confirmed –h1-color overriding default h1 base color | Automatic.css (automaticcss.com)
Contextual Color classes (v2.8) – Issue with Heading colors and utility classes | Automatic.css (automaticcss.com)
Loom extension no longer creates extra space
This fixes the bug reported in ACSS + LOOM Extension | Automatic.css (automaticcss.com)
Contextual color classes are back
Contextual color classes such as .bg–success were no longer being generated. This problem is fixed.
Heading sizes and line heights in Oxygen now produce the correct output
This fixes the bugs reported in H1 elements not using correct size since ACSS 2.8 (Oxygen) | Automatic.css (automaticcss.com)
Accent button is back in the context menu
The context menu was missing the “Accent button” color, which is now back.
Removed references to --variable-grid from our docs