Changelogs

Some leftover CSS was conflicting with the button styles within the builder.

This issue could potentially break your colors on the frontend.

In this version, a new “Find & Replace” bulk action has been added to the Class Manager.
It lets you search for any string used as a value—whether in control settings or custom CSS—within your global classes. This is especially useful when you need to update a variable prefix across multiple classes.

When clicking on a class inside the Class Manager of AT, you now have two different tabs: Class overview and Custom CSS. This improves performance and leaves more room for both the overview data and the CSS editors.

You can now set a custom prefix to any palette created inside the Global Color Manager of AT.

You can now add a custom prefix to all variables, global classes, and global colors used throughout ATF.
However, think carefully before using this feature — if you plan to work with compatible design kits in the future, custom prefixes could lead to conflicts or unexpected issues. It’s strongly recommended to leave the default “at-” prefix and call it a day!

The .clickable-box utility class of ATF has been recategorized in “Accessibily”.

H2 is now the default HMTL tag when adding a heading element to the structure.

Before this release, importing Advanced CSS stylesheets required a manual step to recompile the files and generate the corresponding CSS files. Now, all the Advanced CSS stylesheets imported within the Theme Settings are automatically recompiled, and the CSS gets generated on the fly.

A typo was present in ATF: at-link-cover–hover has been replaced in at-link-color–hover.

Due to recent Chrome changes, we changed the outline-style from “auto” to “solid” throughout the entire framework.

The new builder tweak “Transform all select controls into Comboboxes” was on by default and there was no way to turn it off.

In some rare cases, a PHP error could be generated while saving the clamp settings into the Variable Manager of Bricks.

When opening any AT modal, the search input field wasn’t being autofocused anymore.

Since 3.1, the classes generated by “Imported Classes” weren’t enqueued correctly anymore.

A PHP error was kicking in while importing Advanced CSS global styles & child Theme styles.

The grid utility classes are now fully integrated into the builder via the Class Manager. By clicking the corresponding menu, you can manage all your grid utility classes directly within the builder. Any changes made are instantly compiled without the need to refresh your browser.

All custom CSS related to the responsive grid classes is contained within the Custom CSS control of each global class. This means AT no longer needs to output any custom code, as Bricks handles everything. These classes are now conditionally loaded on each page when required and will function fully even if you choose to deactivate AT.

A new ‘Modify’ option has been added to the bulk actions menu in the Class Manager of AT. This feature allows you to bulk-convert the directional styles of your global classes into logical properties with ease.

A new ‘Restore’ option has been added to the bulk actions menu in the Class Manager of AT. This feature allows you to bulk-restore the global classes sitting in the Trash category.

A new ‘Permadelete’ option has been added to the bulk actions menu in the Class Manager of AT. This feature allows you to permanently bulk-delete the global classes sitting inside the Trash category.

Generate all the relevant CSS variable categories within the Variable Manager with a single click! Each category will be automatically suggested in the CSS Variable Picker based on the control you’re editing. Simply populate the categories with your own variables, and you’re all set!

You can now easily reorder categories in the CSS Variable Manager by simply dragging and dropping them into your desired position.

Advanced Themer uses four CSS variables to manage clamp functions: --min-viewport, --max-viewport, --base-font, and --unit-clamp. Previously, these variables were enqueued by the plugin, creating a dependency that prevented deactivating the plugin without losing styles. Now, they have been migrated and integrated into the CSS Variable Manager, eliminating this limitation. As a result, the corresponding options in the Theme Settings have been deprecated.

A new Color type is now available for variables in the AT Variable Manager, featuring a handy color picker for quick selection and editing.

You can now customize your variable picker to automatically open the most relevant categories based on the CSS category of the control. For example, opening the variable picker in the margin controls will suggest spacing variables, while opening it in the typography controls will show font variables on top of the modal.

All variables set as Colors in the AT Variable Manager are now automatically displayed in the Variable Picker, neatly organized by the categories you’ve created.

You can now filter the structure panel by one of these specific categories: Name, Label, HTML Tag, Global Class, CSS Class, Text Content, CSS ID, Bricks ID, or data-attribute.

You can now look after a specific data-attribute using the filterable structure feature.

The Style & Class indicators in the Structure Panel have been completely rewritten for improved performance — especially to address rendering issues with :before and :after elements introduced in the latest Chrome update.

New keyboard shortcuts are now available inside the Quick Search modal.

When you manually filter the Quick Search modal by a specific category, the filter remains active even after closing the modal. To remove it, you’ll need to disable the filter manually.

A new “Show Generated CSS” view is now available in the Color Manager. This view provides an editor displaying all CSS declarations related to colors generated by AT. It’s especially useful if you ever need to deactivate AT but want to keep your generated colors. Simply copy the CSS code and paste it into Bricks’ global.css to retain your styles.

A new contextual menu has been added to the Color Manager, replacing the header icons to free up space and make room for future features.

The icons that appeared on hover in the Color Manager header are gone — everything is now always visible. The dropdown has been redesigned to include toggles for enabling or disabling each palette, as well as a quick option to set your default palette.

In the initial release, the Color Picker only displayed colors generated by CSS variables. Now, it also includes default Bricks colors that use static values, such as HEX, RGBA, or HSLA, within the modal.

In the initial release, only color palettes containing colors generated by AT were displayed. Now, the Color Picker lists all your palettes.

A global ‘Logical Properties’ converter is now available in Theme Settings. With a single click, you can convert all your directional styles applied to elements and global classes. The converter will scan all elements across posts, pages, templates, components, and global classes.

When the “logical properties” feature is enabled, the Quick Remote Template from AT will automatically convert directional styles to logical properties across all imported elements. This conversion is fully compatible with any external source, including Frames, Bricksmaven, and custom remote libraries.

You can now convert an element’s directional styles to logical properties with a single click using the converter in the Class Contextual Menu.

You can now add an icon to the topbar for instant access to the Quick Remote Template modal, bypassing the AT main menu.

All the darkmode toggles and buttons (nestable or not) are now compatible with both ACSS and Frames.

This new polyfill option allows you to run the scroll() and view() functions on browsers that don’t yet support the animation timelines.

In the initial release, the inline styles related to the page transition were generated on the main file of AT. They are now linked to the specific page transition CSS file, so dequeuing the main AT file won’t impact the page transitions anymore.

Some cache plugins may delay the loading of CSS declarations for dark mode toggles and buttons, causing a layout shift on page load due to the input not being hidden in time. To prevent this issue, an inline display: none is applied to each dark mode input.

To improve performance, all modals generated by AT are no longer loaded on page load. Instead, they are now dynamically mounted only when explicitly opened. This significantly reduces the amount of HTML in the DOM and enhances overall builder performance — especially with the latest version of Chrome.

If you have multiple remote template sources, you may encounter an issue where some become unselectable due to the top bar not being scrollable on wider screens.

Jumping between different elements in the Style Overview modal previously caused the Structure list to scroll back to the top. Now, the scroll position is preserved when switching elements within the Structure Panel.

The global classes with no styles applied weren’t correctly displayed within the Style Overview modal, making it impossible to transfer breakpoint styles between other classes or from the ID level.

Toggling the color palette’s dropdowns within the Color Picker could cause the input to lose focus, and thus, the selected variable wasn’t correctly applied to the builder.

Bricks controls using a popup (such as border, box-shadow, etc) were incorrectly closed when selecting a variable from the CSS Variable Picker.

Exporting/importing partials or custom stylesheets from Advanced CSS using the global Import/Export function of AT could generate a PHP warning.

A typo in the code prevented the Theme Styles from being correctly imported when using the Global import function.

On Firefox, the full-sized editor applied to the code elements wasn’t scrollable when the code was larger than the window.

In some cases, the global query loop selector conflicts with third-party plugins, making the item unselectable within the dropdown.

The admin pages have been excluded from the global page animations. They’re now running only on the frontend.

When deleting a custom category in the CSS Variable Manager, the action wasn’t targeting the correct item, causing unexpected behavior.

Global color variables were being reinitialized despite the corresponding tab in the Theme Settings being disabled. That could cause some color variables to be improperly renamed on builder load.

Using UTF-8 characters in SuperPowerCSS would trigger an unnecessary @charset declaration during the Sass compilation process.

Strict Editor View, Quick Edits, and Builder Tweaks were still visible in the AT Main Menu, even when the corresponding tabs were disabled in the Theme Settings.

Disabling the Builder Tweaks category in Theme Settings did not remove the AT Main Menu from the builder’s top bar as expected. This issue has now been resolved.

HTML tags such as <svg> were getting stripped in the Advanced CSS editor, causing background: url('data:image/svg+xml;utf8',…) to not work correctly.

Previously, the Conditions and Interactions icons in the element panel were only clickable on their SVG paths. Now, the entire block is clickable for improved accessibility and ease of use.

A recent change in the Core Framework’s data structure caused typography and spacing variables to be displayed incorrectly within the Variable Picker.

Pressing the ESCAPE key while the Quick Remote Template modal was active caused an error and prevented the modal from closing as expected.

In the AT Class Manager, the “Active on Page” filter within bulk actions was not properly identifying and filtering classes actively used on the current page.

Page transitions are now entirely CSS-based, with no JavaScript added to the code.

The “target” control has been removed from the Page Transition settings within the Page settings.

The “wrapper” control has been removed from the Page Transitions options within the Element settings. The unique ID is now calculated by pretending the post ID in a query loop context.

Previously, you needed to activate the Page Transition on the page level to add element transitions. This is not required anymore – you can simply set your element transitions without activating the page-level transitions.

A new “animation” icon is now available within the left tab shortcuts.

You can now filter your Structure Panel by HTML tag. Digiting “div” or “span” will return all the elements that use this tag on the current page.

The AI functions within the SuperPowerCSS controls were displayed even without a proper API key set in the Theme Settings, leading to potential errors when processing requests.

Hiding the Structure List inside the Style Overview Modal could break the full-width design.

Converting a Nested Element to a Bricks component from the Nested Element Library did not work as expected, rendering the resulting component uneditable in the builder.

In the Nested Element Library, custom categories with only a few nested elements displayed oversized elements that did not adhere to the grid layout.

The CSS declarations for Global Page Transitions were not enqueued on pages using Gutenberg blocks, such as blog posts.

A typo in the CSS declarations for Global Page Transitions prevented custom keyframes from being applied to the new and old animations.

The Style Overview modal’s structure list displays Class and Style indicators for each element.

A new dot now appears next to each class input in the Class Converter modal, indicating potential conflicts:

Red: The class already exists in the database, potentially affecting other elements beyond those being converted.

Green: The class name doesn’t exist yet, ensuring no conflicts.

Orange: The class name isn’t in the database but appears multiple times in the Class Converter Preview.

The Responsive Helper and Breakpoint Slider are now separate tweaks that can be enabled independently in the Theme Settings:

Breakpoint Slider lets you seamlessly slide between different breakpoints for easier responsiveness testing.

Responsive Helper unlocks 2-click options on breakpoint devices, allowing you to check the minimum and maximum values of each breakpoint in real-time.

The “Set SVG as Default Library for Icons” tweak conflicted with other elements and controls that used icons, causing the setting to be ineffective when selected.

When filtering the Structure Panel with a keyword present in a collapsed item, the element was not correctly displayed in the results.

If the user previously clicked on an iframe element and then selected a right-element shortcut, the element appeared correctly in the iframe but was not reflected in the structure panel.

Previously, components added via right-element shortcuts were placed at the root of the structure, ignoring the active element’s position. Now, the function verifies if the active element is nestable and nests the component inside when applicable.

Certain style controls in the Legacy Dark Mode Button were not applying correctly on the frontend due to CSS conflicts.

When the Breakpoint Slider was expanded in the builder, it caused the bottom of the preview window to stretch by 66px.

The “Lock Elements Order” feature could mistakenly apply incorrect classes to structure elements and allow dragging within non-nestable elements, resulting in the dragged element being removed from the structure.

Switching elements while the Tag Manager was open caused the dropdown to reopen each time the same element was reactivated, disrupting input autofocus.

Applying ‘Hide Element’ on an element defaulted to the Desktop breakpoint, disregarding other breakpoints and mobile-first settings.

Clicking a CSS property from the Uncategorized category in the Variable Picker did not correctly apply the value to the selected control.

Creating new elements using the right elements shortcuts could generate mismatched IDs in the structure panel and iframe, causing JS errors when selecting elements inside the iframe.

Grids with component children weren’t applying ID-level grid-row and grid-column styles, as components can’t have varying styles per instance. Now, the grid builder generates these CSS declarations in the parent element’s Custom CSS field, similar to how it handles classes and query loops.

In some cases, converting a basic text or heading into a rich text element didn’t apply correctly in the structure or could revert to the previous state.

The default link spacing value could be mistakenly applied to fields that don’t support opposite links (e.g., borders) or shouldn’t be linked at all (e.g., box-shadow and text-shadow).

In this version, you can enable a new floating bar at the bottom of the Structure Panel, allowing you to quickly toggle the following options: hide the current element, hide it only inside the builder, or remove it from the frontend.

When the tweak “Remove Default Libraries for Icons” is activated, opening the icon control will automatically select the “SVG” option by default.

When closing the AT Color Picker, the Bricks Color Picker remained open. Now, both are synced to close together.

Inside the quick search modal, you can now filter your structure elements by content keyword. This will return all the elements that contain the keyword inside the text control.

In the quick search modal, you can now filter structure elements by their attached global class names. This will display all elements that have at least one class matching your search term.

When the Responsive Helper tweak is enabled in the Theme Settings, the helper now activated by default on load.

At times, the structure panel and iframe were out of sync when adding new elements from the right-side shortcuts. This issue has been resolved.

When importing a structure from the CodePen Converter without an active element selected in the Structure Panel, the JavaScript function previously returned an error. This has been fixed, and the CodePen structure is now correctly added to the root of the panel.

The Mask Helper tweak stopped working correctly since 3.0: selecting a mask from the modal had zero effects on the element. It has now been fixed.

Clicking on both “Hide the element in the builder” or “Remove the element from the frontend” inside the contextual menu of the Structure Panel would also trigger the “Hide element” function and set the display property to “none”.

Setting a new logo image in Strict Editor View settings previously triggered a PHP warning, potentially resulting in a blank page. This issue has now been resolved.

There was an issue with accordions in the Content tab: when ‘Lock ID Styles’ was enabled, toggling them was impossible unless the lock was disabled.

In rare cases, uninstalling Advanced Themer with the ‘Remove all data when uninstalling the plugin’ option enabled could cause Theme Styles to become deindexed, leading to issues inside the builder.

In the Advanced CSS modal, pressing CMD/CTRL + F would trigger the Quick Search modal instead of the native CodeMirror search function. This issue has now been resolved.

Importing CSS files within the Theme Settings could trigger a PHP warning if the website lacked proper SSL configuration. The function has now been improved to support various server setups.

A conflict existed between the Quick Search keyboard shortcut and Bricks’ native shortcut for focusing on the element settings search. This has now been resolved, and Quick Search will no longer be triggered when the Shift key is pressed.

Previously, selecting a class inside the Structure Panel while a component was present in the Structure Panel could trigger a JavaScript error, causing the right panel to fail to mount correctly. This issue has been resolved, and the Class Manager now works seamlessly with components.”

When searching for a CSS variable in the CSS Variable picker, the results would incorrectly include outputs from the Color Picker. This issue has been fixed.

When setting theme variables within the Variable Manager of AT, the CSS variables were not rendered correctly in the Strict Editor View, causing layout issues that affected editors only.

In rare cases, the right element shortcuts could prevent the AT options from mounting correctly inside the builder – and cause the AT functions to be broken.

Even when you disabled the global colors settings within the Theme Settings, or if you disabled the darkmode on the frontend, the JavaScript file “darkmode-local-storage.js” was still being enqueued on the frontend.

When importing the AT – Theme settings from an export file, the confirmation popup would include duplicate “Theme Settings” strings for each data entry imported.

Importing the AT – Strict Editor View settings from an export file would generate a Fatal Error in the AJAX response due to a typo in the code.

Instead of being fixed on the page, the confirmation popup after importing/exporting/resetting settings was displayed as position:absolute, which wasn’t a great UX on long pages.

Advanced Themer now fully supports the component functions of Bricks since v.1.12.

A new top-right icon within the Structure Helper modal allows you to extend/collapse the inner elements of the components available inside the page.

Clicking on any active filter within the Structure Helper modal will reset the filter and show the structure list without any opacity.

You now have complete freedom to toggle the visibility of any Bricks element using the left-visibility feature in Strict Editor View.

The Right Shortcuts next to the structure panel have been redesigned to feature a new options icon. By clicking this icon, a modal opens where you can easily add or remove elements, including third-party ones. Additionally, you can rearrange the active elements by dragging and dropping them to customize the order. Now, you have complete control over your right shortcuts!

The requests made by ACF to the database went from 284 to… 1!

All the root elements (or parent elements) of each component inside Class Converter have now an active background color. It makes it easier to differentiate on the fly which elements are a parent, and which are children.

When clicking on the skip/include toggle next to a root element (or parent element) of a component, all toggle status will be applied to all the children of that element. This is especially useful when you need to disable an entire inner-component without the need to manually toggle off each child one by one.

A new option has been added in Class Converter to sync the label of each element with the newly assigned global class name.

You now have access to all deleted global classes within the new Trash category in AT’s Global Class Manager. Additionally, you can restore deleted classes directly from the manager or permanently remove them as needed.

In previous versions, the HEX input triggered the color calculation only when you clicked outside the field. Now, hitting the ENTER key or the TAB key will also fire all the functions related to the color calculation.

In previous versions, the HEX input triggered the color calculation only when you clicked outside the field. Now, the functions are executed immediately as soon as a 6-digit HEX code is entered into the input.

You can now open the Variable Picker using both the V icon and right-click events by selecting the ‘Both’ option in the theme settings.

You can now customize the default nested elements using the following PHP filter within your child theme:

// Modify the default nested elements
add_filter('at/nested_elements/default_elements', function($default_elements){
	
	// Example 1: See the data structure of the default nested elements
	var_dump($default_elements);
	
	// Example 2: Remove all the default nested elements
	$default_elements = [];
	
	// Example 3: Add a new nested element.
	$default_elements[] = [
		'id' => 'my_nested_element',
		'label' => 'My Nested Element',
		'icon' => 'ti-id-badge',
		'category' => 'default',
		'default' => true,
		'elements' => [
			// include your nested elements here
			[
				'id' => 'nddjcp',
				'name' => 'block',
				'settings' => [],
				'children' => [],
			]
		],
        
	];
	
	return $default_elements;
});

A new “Convert to Component” icon now appears on all custom nested components. Clicking this icon saves the nested element as a native Bricks component (introduced in v1.12).

You can now customize the default presets in the Box-Shadow modal using the following PHP filter within your child theme:

// Modify the Box-Shadow Presets
add_filter('at/box_shadow/presets', function($presets){
	
	// Example 1: See the data structure of all the default presets
	var_dump($presets);
	
	// Example 2: Remove all the default presets
	$presets = [];
	
	// Example 3: Add a new preset. One array for each layer.
	$presets[] = [
		[
            "rgb" => "255,149,5",
            "alpha" => 0.3,
            "x" => 1,
            "y" => 2,
            "blur" => 3,
            "spread" => 4,
        ],
		[
            "rgb" => "255,149,5",
            "alpha" => 0.5,
            "x" => 5,
            "y" => 6,
            "blur" => 7,
            "spread" => 8,
        ]
	];
	
	return $presets;
});

Recently, many users were unable to see new Bricks elements in the builder. This occurred because if you saved the “Enable / Disable” array in a previous release, where these elements weren’t part of the list, they ended up being unselected in the theme settings, causing them to be hidden in the builder. This was an oversight. Going forward, all elements will be visible by default, and only the ones you choose to disable will be hidden.

Additionally, the elements list is now loaded dynamically, ensuring it always includes the latest elements that can be enabled or disabled in the builder.

In this release, all options in the “Enable / Disable” array will be reset to unchecked, so you’ll need to manually re-select any elements you wish to disable.

If you choose not to adjust these settings, there will be no impact on your site’s frontend. The only change will be that any previously excluded elements will now appear in the builder’s list by default.

All data previously stored in the “AT – Theme Settings” — including Grid Guides Settings, Right Shortcuts Settings, Strict Editor Settings, Nested Elements Library, Global Query Manager Settings, and all Advanced CSS scripts — has now been organized into separate toggles. This allows you to have granular control over which settings you want to import or export. 

You can now import/export new native Bricks data, such as the Bricks Settings, the Pseudo Classes, the Breakpoints Settings, the Structure & the Panel Width.

Within the Plain Classes modal, you can now easily identify locked classes by the lock icon next to each one.

When you open the Plain Classes modal, a trailing space is automatically added to the Editor so you can just start typing the name of the global class you want to add without having to hit the backspace key before.

If a global class is already active on an element, clicking on it within the Plain class modal will remove the class from the list instead of duplicating it.

In some cases, changes made to the Advanced CSS stylesheets were not properly reflected on the frontend due to potential server-side cache issues. To resolve this, a version number will now be added to each stylesheet enqueued by AT, ensuring the stylesheet is correctly refreshed on the frontend.

You can now filter the structure by an element ID. It supports both the CSS ID and the internal Bricks ID. This is particularly useful when you want to jump on an element with a specific ID for debug purposes.

You can now look for components inside the Quick Search Modal. Clicking on a component will add it to your structure panel.

If you enable the “Hide/Remove Element” controls in the Theme settings, two new shortcuts will be visible within the “Hide Element” item in both the Structure Panel and the Class contextual menus. These shortcuts allow you to quickly hide/show an element in the builder and remove/activate it on the frontend without looking at the element panel.

A new set of commonly used builder tweaks can now be toggled on/off within the AT Main Menu without leaving the builder and refreshing the page. For example, if you want to disable the “Lock ID styles” for some time while you’re working on a page, you can disable that specific tweak inside the builder with one click and enable it again at any time.

The SASS compilation logic within the builder has been completely overhauled, significantly reducing resource usage on your computer.

In previous versions, attempting to select an element’s label within the structure panel using the keyboard arrow keys would mistakenly trigger AT’s “Move Element” functions. The script has been updated to ensure it checks if a label is selected before executing any movement actions.

The “Generate Global Query Loop” option in the query loop popup of the builder was previously visible only when a query type was manually selected. Now, it is displayed even when no specific post type is selected.

The Tag Manager has been completely overhauled for improved performance and usability. It now runs more efficiently within the builder, eliminates the previously confusing color indicators (green, orange, red), and lets you input custom HTML tags directly from the structure panel for any elements that support them.

A new structure list has been added to the Style Overview modal, enabling you to effortlessly navigate and manage the styles of all elements on your page without repeatedly opening and closing the modal.

New Keyboard shortcut options have been added for the newly introduced AI Prompt Manager and the Quick Search functions.

A recent update to the ACSS code caused the dashboard icon to overlap with the right shortcut sidebar in AT. The icon is now programmatically repositioned within the structure panel to prevent this issue.

If the selected element contained a global class ID that had previously been purged, the ‘focus on first unlocked class’ script could trigger an error. Now, the script checks if the global class exists in the database before applying the auto-focus.

If your OpenAI API key was not entered correctly in the theme settings, a JavaScript error would appear when opening the ‘Generate AI Structure’ panel.

The icon control within the Icon element was not properly skipped by the class converter, causing its value to reset after the conversion process.

When importing global class settings via the Import function in AT (within the theme settings), the process previously ignored the locked list, resulting in all your classes being unlocked. Now, locked classes are properly included during export and import.

If a nested component contained an element with a global class that had been purged, the script would generate an error during the save process, preventing the component from being saved correctly.

If you’ve written lengthy CSS code in SuperPowerCSS, you may have encountered an issue where the last rows are inaccessible due to an overflow problem. This should now be solved.

In the Color Manager, changing the position of a parent color could cause its corresponding shades to misalign. Now, the shades will automatically adjust to stay correctly positioned under their parent.

In some cases, converting all UX styles to custom CSS controls could result in lost styles due to data not being saved correctly inside the corresponding Bricks objects.

In previous releases, modifying the page.css file in Advanced CSS while the active breakpoint was set to mobile-first would incorrectly place the code under the desktop view. Now, Advanced CSS intelligently detects whether you’re using a mobile-first approach and ensures your CSS is placed in the correct section!

Recent changes in the latest Bricks release may cause control values to display incorrectly (shown as empty) within the builder when the ‘Focus on First Class’ tweak is enabled.

The Rich Text wasn’t easily movable with keyboard shortcuts due to the autofocus being applied on the tinyMCE editor.

There was a conflict between the CodeMirror instance of Bricksforge and the right keyboard shortcuts of AT: typing inside the editor would wrongly create new elements in the structure.

Complex dynamic tags from dynamicooo could be wrongly parsed as a clamp function when the “Autoformat” tweak is enabled.

In scenarios where you switch to elements with locked classes only, the element panel may incorrectly auto-expand in sections where it shouldn’t, leading to a poor user experience.

In scenarios where you switch to elements with locked classes only, SuperPowerCSS could fail to mount correctly and a textarea field would show up instead of the CodeMirror instance.

In some cases, editing a global class using SuperPowerCSS could result in unsaved code due to a conflict with other AT functions.

Adding a global query loop without a category would return an AJAX error in the console. This shouldn’t happen anymore.

Previously, applying focus point settings to a global class while editing an image element would incorrectly apply the settings at the ID level. This issue has now been resolved.

Pressing the CMD+F shortcut while editing CSS code in SuperPowerCSS would incorrectly trigger the Quick Search function instead of the search dialog in the CodeMirror instance. This issue has now been fixed.

The calculation of the available arrow keys for moving an element within the contextual menu of the Structure Panel could previously be inaccurate. This function has now been refined to provide more precise results.

Safari users might have experienced issues when selecting a CSS variable from the CSS Variable Suggestion dropdown in AT, where the newly inserted value would be overridden by the old value as soon as a window event (such as click, blur, mousemove, etc.) occurred. The suggestion dropdown has now been redesigned to prevent this from happening.

When you opened the code element in full-size mode, part of the code remained hidden until you clicked inside the editor. Now, the editor automatically refreshes the content as soon as you enter full-size mode.

With this release, the new Nestable dark mode button and toggles have been introduced, and the old elements are now officially considered Legacy. There are no plans to remove them in the future to maintain backward compatibility. However, it is strongly recommended to use the new nestable elements moving forward.