How to Override Default Submit Spinner in AEM Core Components Adaptive Form | Community
Skip to main content
K
KaramjeetKa
Level 1
February 22, 2026
Question

How to Override Default Submit Spinner in AEM Core Components Adaptive Form

  • February 22, 2026
  • 1 reply
  • 21 views

Hi Team,
I am using AEM as a cloud with Core Components-based Adaptive Forms and integrated form in my aem site. When the form is submitted, a default loading spinner appears.
I would like to customize or replace this spinner so it matches our site’s branding.

Could someone please clarify:
    •    What is the recommended way to override the default submit spinner?
    •    Which CSS class or JS event controls the submitting state?
    •    Should this be handled through a custom client library (Sites or Forms-specific)?
    •    Is there a supported, upgrade-safe approach without modifying /libs?

Any guidance or implementation examples would be appreciated.

Thanks

1 reply

P
Adobe Employee
Pranay_MAdobe Employee
Adobe Employee
February 23, 2026

Hi ​@KaramjeetKa,

Following up on your question about customizing the submit loading spinner for your Core Components–based Adaptive Forms embedded in AEM Sites.

When a Core Components Adaptive Form is submitted, the default loading spinner and “submitting” state are managed by the Core Components client-side runtime. The recommended and upgrade-safe way to customize this indicator is:

  • Do not modify /libs or any OOTB Core Components directly.
  • Instead, use:
    • An Adaptive Form theme (recommended) to override the spinner’s look via CSS, and/or
    • A custom client library (Sites or Forms) for any additional JavaScript behavior (for example, adding your own “submitting” class and brand-specific animation).

In practice:

  1. Inspect the form’s DOM while submitting to identify the submit button and container classes (for example, cmp-adaptiveform-button and the associated “busy” state class).
  2. In your Adaptive Form theme (src/theme.scss), add CSS targeting those classes to hide or replace the default spinner with your branded loading indicator.
  3. Optionally, use a Forms/Sites clientlib to hook into submit success/error handlers to toggle custom state classes and manage advanced UI feedback.

These mechanisms are the supported customization points for Core Components Adaptive Forms on AEM as a Cloud Service and are designed to be upgrade-safe.

For reference, Adobe’s documentation on these areas:

Thanks
Pranay

    Terms & ConditionsAccessibility statement

    Loading footer...