Changelog

You can now control the background-repeat property for textures and overlays.

You can now set blend mode for custom overlays.

You now have 5 options instead of 3 for custom textures/overlays.

Internal mostly.

This is a progressive enhancement for animating keyword values like auto, max-content, etc.

Auto color relationships should be fully compatible with color scheme now.

Auto color relationships should be fully compatible with custom textures and overlays now.

If you’ve been experimenting

You no longer need to add quotes around values manually on textures/overlays two through five.

When the user opened the dashboard for the very first time, the acss_dashboard_position was not set. So when the user pinned the dashboard and refreshed the page, the code tried to read the acss_dashboard_position (what is null) and crashed. This is fixed.

Max-height issue fixed.

You can now use a Texture Style as a background AND as an overlay. ACSS will generate .overlay– classes for each Texture style if you turn on the overlay option.

Some new controls and refinements have been added.

Textures & Overlays will not load any code unless an asset is declared. Even if the feature is turned on, no code is loaded unless you’ve defined an asset for the specific Texture you’re creating. You’re free to leave this feature on at all times with blank assets and it will have zero impact on performance.

The specificity was a little too specific, so we’ve reduced it to the minimum required to work.

Re-mapping default styles to classes using :is() increased specificity for heading selectors. We’ve removed the :is() to reduce specificity back to the standard.

Users can now create custom textures and sync these textures with automatic color relationships. Textures will most often be used for backgrounds, but could also potentially be used for custom overlays. At this time, Textures is an experimental feature located in Options >Experimental > Textures.

Color relationships now includes support for buttons, links, and headings.

3rd party developers (e.g. AT) now have a way to implement ACSS recipe expansion in their interface.

We’ve expanded the font-family control to every heading level independently (1-6).

Turning Gutenberg style support off was still resulting in the enqueuing of automatic-gutenberg. This is no longer the case.

Heading classes were not outputting the font-family. Now they do.

There was a Breakdance-related console error in Bricks in FF Dev. This is resolved.

Background color was missing from “next” buttons in WS Form when using .form--light. This is now fixed.

Fix for header/label clashing in long dashboard screens.

Users can now automatically indicate links that open in a new tab or window with both a visual and auditory cue for better UX and accessibility. We’ll be adding support for SVGs in a future update.

Users can now control the styling of GDPR checkboxes in Fluent Forms. Unfortunately, this won’t fix the atrocity that is GDPR in general.

Users can now use the * selector in textarea inputs in the dashboard without math validation errors.

Improving stability of each release is a top priority. This is yet another part of our process and commitment to stability.

There’s no reason to not smart space content in Gutenberg pages if Smart Spacing is on, so we’ve changed the default behavior.

Gutenberg is a dumpster fire.

Users can now control the opacity of placeholder text in textarea inputs.

When looking at the console, users were seeing some unnecessary, and at times scary-looking, warnings and messages. We’ve cleared out any unnecessary ones to limit instances of emotional trauma.

There was a disturbance in the force when opening the dashboard in Breakdance. We let the hate flow through us, so this should be resolved now.

Sometimes when you searched for a word, you’d see duplicate instances of certain inputs. This didn’t produce the desired feelings of comfort, efficiency, and stability, so we’ve fixed it.