Problem/Motivation

When using the legacy (classic) toolbar, an unnecessary "padding-block-start" is added to the secondary region.

With the "padding-block-start":
Unecessary padding

Without:
Padding removed

CommentFileSizeAuthor
#4 Screenshot 2026-02-10 141756.png120.41 KByashaswi18
#3 3568214-2.patch1.22 KBjsacksick
secondary-region-padding-removed.png140.28 KBjsacksick
unnecessary-padding-secondary-region.png143.04 KBjsacksick

Issue fork gin-3568214

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:

About issue forks

Comments

jsacksick created an issue. See original summary.

jsacksick opened merge request !739

jsacksick’s picture

jsacksick commented
Status: Active » Needs review
StatusFileSize
new 3568214-2.patch1.22 KB

Static patch for use with composer.json.

yashaswi18’s picture

yashaswi18 commented
Status: Needs review » Reviewed & tested by the community
StatusFileSize
new Screenshot 2026-02-10 141756.png120.41 KB

I applied this MR on Drupal 11.3.3. The unnecessary padding-block-start from the top is now removed as expected.

Steps to reproduce / test:

  1. Install the Gin theme and set it as the admin theme.
  2. In Gin theme settings, select Legacy / Classic Drupal Toolbar.
  3. Create content and observe the secondary region, the extra top padding has been removed.

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

  • saschaeggi committed 8bd2b330 on 5.0.x authored by jsacksick 
    Issue #3568214: Remove the unnecessary padding-block-start added to the...

  • saschaeggi committed 82ec76bd on 4.0.x authored by jsacksick 
    Issue #3568214: Remove the unnecessary padding-block-start added to the...
saschaeggi’s picture

saschaeggi
he/him
commented
Status: Reviewed & tested by the community » Fixed

Thanks!

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

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