Fixed right-side pinning incompatibility with Bricks 1.10.3
A recent Bricks updated that allows for resizing the structure panel was not compatible with our pinning feature on the right side. This is now fixed.
Fixed text--l utility setting a default font weight
Using the .text–l utility class would also change the font weight, even when the user had no font weight value in the dashboard for the L text level. This is now fixed.
Adjacent sibling margin removal adjustment for Smart Spacing
We have limited the scope of adjacent sibling margin removal for Smart Spacing. This feature now sets –paragraph-spacing and –flow-spacing to 0 for siblings adjacent to the selected elements.
Fixed auto border-radius toggle being set to "on" on upgrade
Upgrading from previous versions would erroneously turn on the automatic border radius feature. This no longer happens.
Fixed radios/checkboxes spacing having no effect when grid is set (WS Form)
@heading-style() mixin
Apply global heading styles for any specific heading level to a custom selector while ensuring the output is confined only to properties with values set in the dashboard.
Read docs
@text-style() mixin
Apply global text styles for any specific text level to a custom selector while ensuring the output is confined only to properties with values set in the dashboard.
Read docs
Spacing control for radio and checkbox inputs (forms)
We now provide a custom control point for radio inputs and checkboxes in form elements.
MINOR BREAKING CHANGE: Remove duplicate margins (Smart Spacing)
Some smart spacing elements only contain top margin. Others, like figures, blockquotes, and lists, can contain top and and bottom margin.
When elements that contain both top and bottom margin are followed by elements with top margin, it can create duplicate margins.
This was previously solvable by setting a different block margin bottom value, but that’s not a very elegant or “smart” solution.
This feature introduces a new input that allows you to identify block margin elements so that Smart Spacing can remove the top margin from their adjacent siblings (don’t worry, we set a default for you).
MINOR BREAKING CHANGE: If you’re a user who noticed instances of duplicate margin and already accounted for them somehow, this update may cause a change in those margins. If you did not previously account for any duplicate margin issues, this feature will not break anything.
Since users accounting for duplicate margin issues are rare, any spacing issues from this would be very minor, and this setting needs to be on by default for new users, we’re not introducing a toggle or a blank default value to ensure backward compatibility.
Dashboard scripts now load in footer and delay by default
This improves compatibility with other plugins as well as the WordPress Interactivity API.
Fixed user shortcut panel breaking
Improved front-end data validation (Step 1 of 2)
We have taken the first big step toward perfecting our front-end validation, which ensures that users are not able to save breaking values to the database. There are a few little validation quirks to work out before we can release step 2, which is the final step and will result in full front-end validation.
Concentric Radius Recipe
@concentric-radius; will now expand out the recommended code for creating concentric radii wherever needed.
License Activation Support for WordPress Studio
We’ve fixed issues related to license activation for anyone using WordPress Studio.
Automatically Exclude Header Images from Auto Radius
We’ve updated the default behavior of auto radius to exclude the header. This will prevent logos from automatically having auto radius applied. Users will need to click the default reset icon next to the “Auto Radius Selectors” input under “Additional Radius Options” to receive this update on existing installs.
WP-Admin Top Link Now Takes Users to Front End
Rather than reloading the admin page, the toolbar link in the admin will now take users to the front-end and trigger the dashboard to open. This should reduce confusion and increase efficiency.
Fixed Bricks form checkbox label color on hover
We fixed an issue with the hover label color on checkbox elements in Bricks forms not being styable from the dashboard.
Fixed form label padding
Label padding was not updating via the dashboard, especially when “inside position” was used as the label position. This is now fixed.
Fixed an issue with .grid--auto-rows causing items to stretch
.grid--auto-rows is a rarely used class that was causing all items in a grid to stretch (instead of just doing its intended job). This is now fixed.
Fixed an issue with .grid--auto-rows breaking auto grids
.grid--auto-rows is a rarely used class that was causing all auto grids to go to a single column layout. This is now fixed.
Fixed an issue with alt color partials not receiving dashboard updates
Enhanced width options in context menus
Added 100%, fit-content, min-content, max-content, and auto as quick-values in context menus for width inputs.
Added 1px offset to @breakpoint-up mixin
We added a 1px offset to the breakpoint-up mixin to ensure that there is zero overlap with max-width media queries.
Added tooltip to hover state icons next to inputs
Some users weren’t immediately sure what the hover icon was for. We’ve added a tooltip for clarity.
Fixed the no-value/value issue on some inputs on upgrade from 2.x
Note: A database backup is recommended prior to updating due to this bug fix.
This bug affected multiple different inputs where the SCSS variable has a blank value, expecting to get its default value from the dashboard. The default dashboard value is now pushed to the SCSS variable properly, fixing the issue with missing styles on upgrade.
This bug only affected upgrade installs and was fixable quickly by resetting the affected dashboard values, but the reset fix should no longer be needed.
Added radius--circle and --radius-circle back to context menus
This value slipped out of the context menu for a while, but it’s back now.
Fixed an issue with auto-grid gaps in Oxygen Builder
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 ";"