Changelog
Keep track of what's new with ACSS! For details on specific features and utilities, please check the official documentation.
- November 19, 2024
3.2.4
Hotfix for shade saving action
A seemingly unrelated change to value reversion was affecting the saving of shades. This is now fixed.
- November 19, 2024
3.2.3
General dashboard stability improvements
More small dashboard stability improvements.
Use button styles on Fluent Forms radio elements
Fluent Forms allows users to turn radio elements into buttons. ACSS now supports the use of ACSS button styles in this context.
Fix media targeting in Card Framework
The Card Framework was targeting card media elements improperly, causing media wrappers and other media related elements to receive targeting also. This is now fixed.
Fixed external link arrow indicator on iOS devices
Users should reset the external link indicator HTML entity code to the new default value in the dashboard to apply this fix.
Potential fix for centering classes in Oxygen
Make sure you read this: Oxygen Notice.
- November 15, 2024
3.2.2
Small update to address the lingering “save changes” notice. Expect one more minor release early next week to fix a small dashboard pinning position glitch. With the complete refactoring of pinning, we’re having to go back through and handle the same edge cases with various builders and contexts as we did with the initial dashboard release.
Fix the browser-triggered save changes notice when changes are already saved.
.center--self classes no longer apply any flex properties other than align-self: center
- November 15, 2024
3.2.1
This is a hot fix to address a few back-end issues mostly related to live preview and dashboard logic. None of the reported 3.2 issues affect front-end / visitor experience.
Allow updating of plugin via wp-cli
You can now update the plugin via wp-cli.
Load live preview code only when needed.
Live preview code was persisting, causing some discrepancies between back-end preview and front-end reality.
Fix setting change indication behavior
The setting dot was not properly indicating and was triggering a “you have unsaved changes” message. We’ve also increased the size of the indicator, added an outline for when changes need to be saved (for better accessibility), and tweaked indication colors to pass contrast checks.
Fix for input display logic based on toggles that hide inputs
This was a JSON duplicate ID issue causing the logic to not work. All fields were displayed at all times rather than responding to options toggles. Nothing critical, but annoying.
Fix for input value quote wrapping
Some input values need to be wrapped in quotes and weren’t being wrapped properly. This is now fixed.
Forms: Fix Bricks form message margin
Set default icon sizes in Icon Framework
Defaults were all the same – they’re now set properly.
Remove isolation-isolate from Card Framework
This was causing issues with modals fired from inside cards.
- November 14, 2024
3.2
Attention: This update contains a lot of refactoring to dashboard interactions, including pinning, live preview, calculations, and validation. It has been extensively tested, but we recommend updating on a staging server first and verifying the update before updating on production. If you do update production and encounter issues, it’s perfectly safe and easy to roll back to the previous version. Make sure you report any issues you encounter to our team in the community.
Card Framework (Experimental)
A powerful new framework for managing card styling across your project.
Icon Framework (Experimental)
Users can easily control the global styling of icons now and manage custom icon styling easier at the template, page, box, and single-icon levels.
Completely refactored dashboard docking, pinning, and resizing
It should now be impossible for the dashboard to appear off the screen and the dashboard position will be re-checked every time the window size changes. Additionally, docking and pinning is much more accurate and dashboard height is sticky.
Minor UI/UX enhancements
- The dashboard header is now sticky
- There’s a back button when searching
- Search accordions reveal additional details
Custom SCSS panel is now fully resizable
Users can now drag either side of the dashboard to make it wider when the custom SCSS panel is open.
Updated most important components and logic to Svelte 5
Cleanup and standardization.
Refactored settings logic for better maintainability
Cleanup and standardization.
Padding Breakpoint Classes
You can now change padding at breakpoints with padding utility classes.
Expanded Opacity Values (Increments of 5)
Opacity classes have moved from increments of 10 to increments of 5.
BREAKING: Remove Link Color Manipulation From Contextual Text Color Classes
.text--darkand.text--light(and similar) used to alter the color of links also. This was deemed undesirable by users, so we’ve removed this. These classes will no longer change your link color. You can still change link color using.link--classes.Refactored: Centering Classes
Cleanup and standardization.
Added Centering Mixin
You can now easily center content with the powerful new centering mixin.
Refactored: Display Classes
Cleanup and standardization.
Refactored: Margin Classes & Added Block/Inline Classes
Cleanup and standardization, plus added
.margin-block--and.margin-inline--classes to round out the options with margin classes.Refactored: Visibility Classes
Cleanup and standardization.
Refactored: Position Classes
Cleanup and standardization.
Re-organized: Spacing Classes
File system cleanup and standardization.
Form Fixes
- Inline-start padding for phone fields
- Removed padding bottom default that was causing issues in Bricks forms
- Removed duplicate border-color property in Bricks checkboxes
MINOR VISUAL CHANGE: Fixed an issue with mobile padding calculation for XS and S sizes
The XS and S spacing sizes were dividing by the desktop spacing scale value instead of the mobile spacing scale value. This issue has likely been present since the mobile scale was introduced over 2+ years ago.
Overall, this is a minor issue and any visual differences on mobile should be imperceptible to real users. In fact, it’s so imperceptible that nobody has reported it over this time period.
We’re talking a 2-3 pixel difference in small padding, gap, etc. The fix will actually make your mobile padding more accurate to what you were wanting in the first place, but again, is imperceptible to anyone who doesn’t know what the actual calculated values are supposed to be.