Imported classes from the Class Importer in the Theme Settings could sometimes be removed from the elements they were applied to in the builder.

Minor UX issues in the builder related to specific css applied when pseudo-element shortcut were not active.

Forcing the color Theme to dark in the Theme Settings > Global colors could potentially fail and still show the light theme.

When setting the base breakpoint to Mobile First in Bricks, CSS declarations saved inside the page.css stylesheet of Advanced CSS were applied correctly in both the builder and the frontend, but disappeared from view after refreshing the builder.

The keyboard shortcuts for the builder tweaks Grid Guides, Xmode, Contrast Checker and Darkmode weren't triggering the corresponding functions since version 3.3.

Fixed an issue where the Color Picker library used by the Color Manager was rounding hex values too aggressively when converting to RGB, resulting in possible slightly incorrect color outputs.

Fixed a PHP warning that could appear on first installation before Theme Settings were saved.

A recent change in Bricks 2.1 lead to breaking the AJAX call to the remote templates, thus the Quick Remote Template feature stopped working correctly.

In the Class Manager of AT, renaming a global class while the class was active in the builder could possibly revert to the old name as soon as another class was being activated.

When the event of the AT variable picker was set to "right-click", clicking on the native Bricks CSS icon to open the native variable dropdown would also trigger the variable picker from AT.