Documentation

Fix Rich Text Editor Button Issues After Migrating to CoralUI3

Last update: Wed Nov 19 2025 00:00:00 GMT+0000 (Coordinated Universal Time)

Migrating custom dialogs and client libraries from CoralUI2 to CoralUI3 in Adobe Experience Manager as a Cloud Service (AEMaaCS) causes rich text editor buttons for font, size, and color to stop working. This issue occurs when developers update resource types without verifying compatibility with CoralUI3. To resolve the issue, manually review and update all custom dialogs and client libraries for CoralUI3 compatibility.

Description description

Environment

  • Product: Adobe Experience Manager as a Cloud Service (AEMaaCS) – Sites
  • Scenario: Migration from granite/ui/components/foundation to granite/ui/components/coral/foundation

Issue/Symptoms

  • After migrating from CoralUI2 to CoralUI3, rich text editor buttons for font, size, and color fail to apply changes.
  • Updating sling:resourceType values from foundation components to coral foundation components breaks styling functionality in dialogs.
  • Custom dialogs and client libraries referencing CoralUI2 components stop working as expected after migration.
  • Rich text editor features appear but do not execute formatting actions in migrated dialogs.

Resolution resolution

Follow these steps to resolve the issue:

  1. Review the official CoralUI2 to CoralUI3 migration documentation for required changes and supported components.
  2. Inspect each custom dialog and client library implementation to confirm compatibility with CoralUI3 standards.
  3. Avoid direct resource type replacements; validate every migrated component for CoralUI3 compatibility and update related client libraries to ensure proper functionality.
  4. Refactor or replace any plugins or components removed or altered in CoralUI3 according to official recommendations.
  5. Test all affected dialogs and rich text editor features thoroughly after making manual adjustments.
  6. After migration, test the font, size, and color buttons to ensure they work correctly. Finalize deployment only after confirming functionality.

Note: Some CoralUI2 plugins or components are removed or changed in CoralUI3. Refer to the migration documentation for unsupported features. Automated replacements are not sufficient; perform a manual review.

recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f