Skip to content

Comments

Fix: Inconsistent vertical spacing in “At a Glance” widget between he…#10992

Open
OpuRockey wants to merge 2 commits intoWordPress:trunkfrom
OpuRockey:fix/inconsistent-vertical-spacing-in-at-a-Glance-widget-between-heading-and-content
Open

Fix: Inconsistent vertical spacing in “At a Glance” widget between he…#10992
OpuRockey wants to merge 2 commits intoWordPress:trunkfrom
OpuRockey:fix/inconsistent-vertical-spacing-in-at-a-Glance-widget-between-heading-and-content

Conversation

@OpuRockey
Copy link

Ticket : https://core.trac.wordpress.org/ticket/64682

Summary

This patch standardizes the vertical spacing between the heading and the first content item in the “At a Glance” admin dashboard widget to match the spacing conventions used by other dashboard widgets.

Description

The “At a Glance” widget currently exhibits noticeably larger vertical spacing between the widget title and its first content line (e.g., “1 Published post”) compared to other dashboard widgets. This inconsistency affects the visual rhythm of the admin dashboard and deviates from expected UI spacing standards.

This change adjusts the relevant CSS styles so that the spacing between the heading and content aligns with other widgets, improving visual consistency and coherence within the Dashboard.

Changes Included

  • Modified CSS for the “At a Glance” widget to reduce the vertical spacing between the widget heading and the first content element.
  • Ensured the updated spacing matches that of other core dashboard widgets for a consistent layout.
  • No functional behavior changes beyond visual spacing adjustments.

Rationale

  • Corrects a UI inconsistency introduced in the admin dashboard layout.
  • Aligns the “At a Glance” widget with existing spacing conventions for better visual harmony and user experience.

Testing

  • Verified the updated spacing on a clean install of WordPress trunk (7.0), default theme, and no active plugins.
  • Confirmed that the adjusted spacing matches other dashboard widgets without visual regressions.

Screenshot

image

@github-actions
Copy link

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

Core Committers: Use this line as a base for the props when committing in SVN:

Props opurockey.

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

@github-actions
Copy link

Test using WordPress Playground

The changes in this pull request can previewed and tested using a WordPress Playground instance.

WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Some things to be aware of

  • All changes will be lost when closing a tab with a Playground instance.
  • All changes will be lost when refreshing the page.
  • A fresh instance is created each time the link below is clicked.
  • Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
    it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant