Using the Field Groups Tabs/Tab configuration, mulit-value fields are getting cut off in the Claro admin theme. We observe this issue after core update from drupal10.0.11 to drupal10.1.x. It was working fine before upgrade.

Steps to reproduce

⁠Enable Claro admin theme
Install the field_group module
Create a 'test' taxonomy
Add a entity referenced field for 'test' taxonomy to content type 'article' and choose 'unlimited' in field settings
Set up a Field Groups Tabs/Tab (vertical tab)configuration to 'article' content
Go to node/add/article add form

Issue fork drupal-3414751

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

Sana.Neyazi created an issue. See original summary.

Sana.Neyazi’s picture

Issue summary: View changes
Sana.Neyazi’s picture

Title: Mulitvalue field items are getting cut off in the Claro admin theme » field_group + claro theme - Multi-value fields are getting cut off on the node add form
Sana.Neyazi’s picture

Issue summary: View changes
Sana.Neyazi’s picture

Title: field_group + claro theme - Multi-value fields are getting cut off on the node add form » field_group + claro theme - Multi-value fields are getting cut off on node add form

shalini_jha made their first commit to this issue’s fork.

shalini_jha’s picture

StatusFileSize
new18.13 KB

Hi, i have tried to reproduce this issues same as the steps provided .but i am not able to reproduce the issue.
I am trying with 10.2.0.can you please let me know if i am missing something. or can you describe more.
attaching screen shot for your reference.

Sana.Neyazi’s picture

Hi @shalini_jha This issue is with drupal 10.1.x and field_group 3.0

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 11.x-dev » main

Drupal core is now using the main branch as the primary development branch. New developments and disruptive changes should now be targeted to the main branch.

Read more in the announcement.

quietone’s picture

Status: Active » Postponed

The Claro theme was approved for removal in #3576460: [policy, no patch] Deprecate and remove Claro.

This is Postponed. The status is set according to two policies. The Remove a core extension and move it to a contributed project and the Extensions approved for removal policies.

The deprecation work is in #3576668: [meta] Tasks to deprecate Claro and the removal work in #3584638: [meta] Tasks to remove the Claro theme.

smustgrave’s picture

Project: Drupal core » Claro
Version: main » 3.0.x-dev
Component: Claro theme » Code
Status: Postponed » Postponed (maintainer needs more info)
Issue tags: +Needs issue summary update

Claro has moved to contrib