---
title: "Site Studio 8.2.2 - December 10, 2025"
date: "2025-12-10T07:37:49+00:00"
summary:
image:
type: "announcement"
url: "/drupal-starter-kits/add-ons/site-studio/release/2025-12-10/95591-site-studio-822-december-10-2025"
id: "e33a1b85-13a1-41b5-a7ee-50ed457ec261"
---

Table of contents will be added

Last updated: 10th December 2025  
Released: 10th December 2025

Important

When you upgrade your website to the latest version of Acquia Site Studio, database updates are applied. This prevents the database from rolling back to the previous version.

Acquia recommends that you apply updates in your development environment and back up your website, including the database, before you upgrade Acquia Site Studio.

*   [Bug fixes](#bug-fixes)

Bug fixes
---------

### CKEditor Source view data loss

#### What is it?

Fixed an issue where content entered in CKEditor 5 Source mode can be lost when you switch back to visual mode. This issue was due to a debounce bug in CKEditor’s `onChange` handler.

#### What impact will there be?

Content entered in Source mode is now preserved when users switch between source and visual modes. This prevents data loss.

#### What actions do I need to take?

Run a Site Studio import to ensure the updated JavaScript assets are loaded.

#### Are there any risks I should be aware of?

None.

### Range slider flickering and erratic behavior in some browsers

#### What is it?

Fixed flickering and unexpected value jumps on range sliders in some browsers. The issue impacted gradient percentage sliders and component settings using range sliders.

#### What impact will there be?

Range sliders now move smoothly and allow users to set precise values.

#### What actions do I need to take?

Run a Site Studio import to apply the updated JavaScript assets.

#### Are there any risks I should be aware of?

None.

### Element default styles did not apply correctly

#### What is it?

Fixed a bug where default element CSS included in the page had an incorrect media attribute. This caused styles not to apply as expected.

#### What impact will there be?

Default element styles now apply correctly based on the active media query. Site Studio layouts display as expected.

#### What actions do I need to take?

Run a Site Studio rebuild if you experienced layout issues due to style application problems.

#### Are there any risks I should be aware of?

None.

### Form submission error with button elements

#### What is it?

Fixed a JavaScript error that caused component form submissions to fail when using Drupal core's [button patch](https://www.drupal.org/project/drupal/issues/1671190). The form submission handler now correctly searches for both `<input>` and `<button>` elements.

#### What impact will there be?

*   Component forms work correctly with both `<input>` and `<button>` submit elements.
*   Sites that use the Drupal button patch will no longer experience submission errors.
*   No changes to standard input-based submit behavior.

#### What actions do I need to take?

None. The fix is automatic and backward compatible with all form configurations.

#### Are there any risks I should be aware of?

None. This fix maintains compatibility with both standard Drupal forms and patched forms.

### Image uploader field overlaps text in background image style

#### What is it?

Fixed an issue where the image uploader field configured as **Background image style** displayed an overlapping `figcaption` element that contained the image filename. This caused text overlap issues in component forms, particularly affecting background and foreground hero components. The `figcaption` element is now hidden when the image uploader is used as a background image style, while it remains visible in standard file browser mode.

#### What impact will there be?

*   Image uploader fields in **Background image style** no longer display image filename labels or cause text overlap.
*   Standard file browser fields remain unchanged.
*   Background image preview displays with correct aspect ratio and alignment.

#### What actions do I need to take?

None. The fix is automatic and applies to all image uploader fields configured as background image styles.

#### Are there any risks I should be aware of?

None. This fix only affects the UI of image uploader fields and does not change any features or data handling.

### Keyboard navigation ignores target attributes on menu links

#### What is it?

Fixed an issue where keyboard navigation did not respect target attributes, such `as _blank`, on Site Studio menu links.

#### What impact will there be?

Keyboard navigation now respects target attributes. This improves accessibility and user experience.

#### What actions do I need to take?

Run a Site Studio import.

#### Are there any risks I should be aware of?

None.

### Large desktop breakpoint icon does not render correctly in Style Builder

#### What is it?

Fixed a UI issue where the large desktop breakpoint icon did not render correctly.

#### What impact will there be?

The icon displays correctly in the Style Builder.

#### What actions do I need to take?

Run a Site Studio import.

#### Are there any risks I should be aware of?

None.

### Forward revision token replacement in Layout canvas

#### What is it?

Fixed an issue where tokens inside Site Studio layout canvas components did not resolve values from forward (non-default) revisions. Token replacement now uses the correct parent entity revision.

#### What impact will there be?

Draft and forward revisions display token values from updated fields in those revisions. Reviewers see complete content during moderation.

#### What actions do I need to take?

None. Tokens in draft or forward revisions render as expected after update.

#### Are there any risks I should be aware of?

None.

### Icon Picker component preview rendering

#### What is it?

Fixed the Site Studio Icon Picker component to ensure icon previews render correctly with proper font family handling and improved state management.

#### What impact will there be?

*   Icon previews display correctly in the picker and form fields.
*   State synchronization is improved.
*   Enhanced reliability with proper null or empty checks for icon data.
*   Data attributes are added for testing and debugging.

#### What actions do I need to take?

None. The fix is automatic and backward compatible.

#### Are there any risks I should be aware of?

None.

### Escape HTML toggle not being respected for input fields

#### What is it?

Fixed an issue where the **Escape HTML** toggle on input fields was not respected.

#### What impact will there be?

Input fields with **Escape HTML** enabled now properly escape HTML characters.

#### What actions do I need to take?

None.

#### Are there any risks I should be aware of?

None.