Endless page reloading issue with field_group tabs

Created on 7 January 2024, 6 months ago
Updated 4 April 2024, 3 months ago

Problem/Motivation

D10.2.1, field_group with patch

If placing a block (of a viewfield) inside a field_group's tab the automatically reloading of ajax does not work correctly. One gets stuck in an endless reloading loop.

Steps to reproduce

field_group has a default behavior of always opening the default tab upon page reload. There is a simple patch which fixes this perfectly.
https://www.drupal.org/project/field_group/issues/3130339 🐛 Horizontal/vertical tabs set default tab to last item with #open = TRUE Needs work

On a page with multiple tabs (of field_group) e.g. tab1 and tab2 - placing a block view with intersection explorer on tab2 breaks the functionality in the following way:

Load the page. Click on tab2; the block gets focus and loads correctly. Scroll down and trigger autoload. The page reloads and opens tab1. tab2 has lost focus but the page keeps reloading in an endless loop.

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

💬 Support request
Status

Fixed

Version

1.7

Component

Code

Created by

🇦🇹Austria maxilein

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @maxilein
  • Status changed to Fixed 3 months ago
  • 🇮🇩Indonesia gausarts

    Thank you.

    Playing nice with other modules is no bugs :)

    I have not used field group for quite while. It does have a few issues with my modules like gridstack, blazy lightboxes, slick, and this one as reported elsewhere.

    This is likely about tabs using display: none which caused the issues. In this case you can override with display:block !important, and toggle tab panes class with visually-hidden class instead.

    I may be able to support that module when I have a client which requires it.

    Without any sponsors, this is more about custom works, I am afraid.

  • Automatically closed - issue fixed for 2 weeks with no activity.

Production build 0.69.0 2024