Skip to main content
M
Momoyo_Nakanishi
Level 2
May 27, 2026
New

Issue where the view returns to the first page after editing components on second or subsequent pages in Tab/Accordion components

  • May 27, 2026
  • 2 replies
  • 38 views

When using Tab or Accordion components in a page, an issue occurs where, after editing a component on the second or subsequent pages and then closing it, the view unintentionally returns to the first page.

Expected behavior: When editing components on the second or subsequent pages, the user should remain on the edited page and be able to continue working without being redirected to the first page.

    2 replies

    S
    Adobe Employee
    SubbaraoGa1Adobe Employee
    Adobe Employee
    May 27, 2026

    Hello ​@Momoyo_Nakanishi 

    We’ve analyzed the behavior where editing a component in a Tabs/Accordion on the second or later panel causes the editor to jump back to the first panel/top of the page.

    This is a known product issue related to scroll and focus handling in panel-based components. Adobe has already addressed similar problems in recent AEM versions (for 6.5 in SP24 and later; for Cloud Service in recent monthly baselines).

    GUIDES-32520
    SITES-32621
    Internal Jira for these issues.
     

    Recommended action:
    • If you’re on AEM 6.5, we recommend upgrading to 6.5.24 or later, where multiple page editor jump/scroll issues have been fixed.
    • If you’re on AEM as a Cloud Service, please ensure your program is on the latest baseline.

    Until you are on a fixed version, the best workaround is to use the Content Tree to quickly re‑select the panel after closing the dialog, or to implement a small customization that restores the active panel after editing.

    If you share your exact AEM version and deployment type (Cloud/AMS/On‑prem), we can confirm whether you’re already on a fixed baseline.

    M
    Momoyo_NakanishiAuthor
    Level 2
    May 27, 2026

    Hello, ​@SubbaraoGa1 
    Thank you for your response.
    The environment I am using is AEM as a Cloud Service.

    S
    Adobe Employee
    SubbaraoGa1Adobe Employee
    Adobe Employee
    May 27, 2026

    ​@Momoyo_Nakanishi 

    Thanks for reporting the behavior where, after editing a component inside a Tab or Accordion on the second (or later) panel, the editor jumps back to the first panel.

    We’ve investigated and can confirm:

    • This is a known limitation in the current AEM as a Cloud Service page editor UI, related to how focus/scroll state is handled for panel‑based components (Tabs, Accordions, etc.).
    • It is not caused by your project code or configuration, and it affects only the authoring experience, not the published site.

    Current Status

    • On AEM as a Cloud Service, fixes and improvements for this type of issue are delivered via the regular monthly Cloud Service releases.
    • There is no separate hotfix we can apply on a single environment; the behavior is addressed centrally and rolled out through the platform baseline.

    Recommended Actions

    1. Stay on the latest Cloud baseline
      Please ensure your environments are running on the latest AEM as a Cloud Service release. Adobe continues to improve the page editor in these monthly updates.

    2. Operational workaround for authors
      Until a product fix is available, authors can:

      • Use the Content Tree to re‑select the tab/panel they were working on after closing the dialog.
        This avoids manual scrolling and is the most practical way to continue authoring when the jump occurs.

    3. Ongoing tracking
      We will keep this behavior tracked internally as a UI defect for panel containers on AEM as a Cloud Service, and align it with the Cloud release train.

    M
    Momoyo_NakanishiAuthor
    Level 2
    May 27, 2026

    ​@SubbaraoGa1 
    Thank you very much for your response.
    We would also like to express our sincere appreciation for your continued support.

    We hope that the usability will be further improved through future updates to AEM as a Cloud Service, and we will continue to monitor the situation closely.

    Terms & ConditionsAccessibility statement

    Loading footer...