Problem/Motivation

Use of heading tags improves usability for site visitors using screen readers, as they can request a list of headings. It may be appropriate for some field labels to be rendered as a heading in order to place that field label in the heading list.

Please add a field to /admin/structure/types/manage/[content type]/display to allow overriding div with any one of h2 through h6.

Steps to reproduce

1. Go to /admin/structure/types/manage/page/display

Expected result: Can choose whether to wrap a field label in div, h2, h3, h4, h5, or h6
Actual result: No option as to how a field label would be wrapped

Proposed resolution

Add column for wrap tag.

Remaining tasks

User interface changes

Add column for wrap tag.

API changes

Data model changes

Add field for wrap tang.

Release notes snippet

Issue fork drupal-3277785

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

Charles Belov created an issue. See original summary.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.0-alpha1 was released on May 6, 2022, which means new developments and disruptive changes should now be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

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

Drupal 9.5.0-beta2 and Drupal 10.0.0-beta2 were released on September 29, 2022, which means new developments and disruptive changes should now be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

joaopauloc.dev’s picture

Assigned: Unassigned » joaopauloc.dev

mgifford’s picture

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, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

joaopauloc.dev’s picture

Assigned: joaopauloc.dev » Unassigned
mgifford’s picture

Category: Feature request » Bug report
Status: Active » Needs review

I think this is a bug and that there is code to be reviewed.

needs-review-queue-bot’s picture

Status: Needs review » Needs work
StatusFileSize
new90 bytes

The Needs Review Queue Bot tested this issue. It no longer applies to Drupal core. Therefore, this issue status is now "Needs work".

This does not mean that the patch necessarily needs to be re-rolled or the MR rebased. Read the Issue Summary, the issue tags and the latest discussion here to determine what needs to be done.

Consult the Drupal Contributor Guide to find step-by-step guides for working with issues.

libbna’s picture

Assigned: Unassigned » libbna

The issue is on 11.x verison also so I will create a new MR against 11.x as, MR !3329 is against 10.1 version.

libbna’s picture

Assigned: libbna » Unassigned

When I am checking out to new branch that I have created all the files gets removed, don't know why. I am unassigning myself for now so that someone can guide me what exactly the issue is!! Thanks!

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.