The spacing between titles, tables, action buttons is all different.

CommentFileSizeAuthor
#44 After patch FV..png65.46 KBAamir M
#44 Before patch FV..png73.77 KBAamir M
#44 After patch FV.png72.43 KBAamir M
#44 Before patch FV.png76.4 KBAamir M
#44 Patch FV.png189.13 KBAamir M
#42 Screenshot after patch..png859.39 KBambikahirode
#42 Screenshot before patch..png817.44 KBambikahirode
#42 Screenshot after patch-.png823.27 KBambikahirode
#42 Screenshot before patch-.png814.01 KBambikahirode
#41 test-vertical-rhythm-2487027-41.patch5.01 KBakshayadhav
#41 rerolled_diff_31-41.txt2.5 KBakshayadhav
#41 messages-RTL-after.png571.3 KBakshayadhav
#41 messages-LTR-after.png578.29 KBakshayadhav
#41 messages-RTL-before.png581.22 KBakshayadhav
#41 messages-LTR-before.png597.7 KBakshayadhav
#41 form-actions-styles.png327.41 KBakshayadhav
#36 Screenshot from 2022-07-25 18-27-31.png259.86 KBAamir M
#36 After patch structure.png72.43 KBAamir M
#36 Before patch structure.png76.4 KBAamir M
#36 After patch views.png92.04 KBAamir M
#36 Before patch views.png105.01 KBAamir M
#34 2487027-after-patch.png234.34 KBHarish1688
#34 2487027-before-patch.png294.72 KBHarish1688
#31 interdiff_27-31.txt788 bytesravi.shankar
#31 2487027-31.patch4.92 KBravi.shankar
#28 After Patch 2487027 Content.png340.37 KBchetanbharambe
#28 After Patch 2487027 Config.png352.07 KBchetanbharambe
#28 After Patch 2487027 Structure.png312.36 KBchetanbharambe
#28 Before Patch 2487027 Config.png358.13 KBchetanbharambe
#28 Before Patch 2487027 Structure.png316.24 KBchetanbharambe
#27 2487027-27.patch4.92 KBkiran.kadam911
#26 vertical-rhythm-after.png141.17 KBrinku jacob 13
#26 vertical-rhythm-before.png148.72 KBrinku jacob 13
#23 test-vertical-rhythm-2487027-23.patch4.92 KBbandanasharma
#16 vertical-rhythm-structure.png329.54 KByoroy
#16 vertical-rhythm-content-list.png283.03 KByoroy
#16 vertical-rhythm-configuration.png294.26 KByoroy
#13 test-vertical-rhythm-2487027-13.patch4.8 KBtracipotocnik
#10 test-vertical-rhythm-2487027-10.patch4.18 KBtracipotocnik
#10 vertical-spacing.jpg456.1 KBtracipotocnik
#1 Screen Shot 2015-05-11 at 14.49.58.png73.33 KBBojhan

Issue fork seven-2487027

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

Bojhan’s picture

Issue summary: View changes
StatusFileSize
new73.33 KB

Bojhan’s picture

Assigned: Unassigned » lewisnyman
Priority: Normal » Major

Lewis, I am thinking we need a baseline we use as guideline here. I am expecting 18, perhaps 20? What do you think it should be?

Marking this major as our design will look much better, if solved properly.

lewisnyman’s picture

Version: 8.0.x-dev » 8.1.x-dev
Assigned: lewisnyman » Unassigned
Category: Bug report » Task
Priority: Major » Normal

@Bojhan It's very hard to call this a major, at least in the communities definition of major.

The major priority is used for issues that are not critical, but that do have significant impact or are important by community consensus.

Compare this with... fixing a significant-but-not-critical UX issue and you'd have to say normal at best. This is a perfect candidate for a task in 8.1.x.

Bojhan’s picture

Oke, but what about my other question :D?

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.0-beta1 was released on March 2, 2016, which means new developments and disruptive changes should now be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

yoroy’s picture

Issue tags: +Needs design

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.0-beta1 was released on August 3, 2016, which means new developments and disruptive changes should now be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.0-alpha1 will be released the week of January 30, 2017, which means new developments and disruptive changes should now be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

james.mejia’s picture

I think the easiest way in establishing rhythm would be to stick consistent units of vertical spacing. So based on 81.3%/1.538em, we should have units of 10px, 20px, and multiples of those.

Some elements (like paragraphs) use 1em for spacing when they should be using 10px/20px/30px/40px.

tracipotocnik’s picture

Status: Active » Needs review
StatusFileSize
new456.1 KB
new4.18 KB

Took a stab at fixing the heading/paragraph/button spacing.

Page Titles: 15px
Breadcrumbs: 20px
Paragraphs: 10px
Headings: 20px
Form Items (except checkboxes): 20px
Checkboxes: 10px

Visual for the before/after attached.

Status: Needs review » Needs work

The last submitted patch, 10: test-vertical-rhythm-2487027-10.patch, failed testing.

idebr’s picture

@traci.potocnik@gmail.com Thanks for working on this issue! It seems your commit is missing the file core/themes/seven/css/components/action-links.css. Can you check if you still have this file available in your repository?

tracipotocnik’s picture

StatusFileSize
new4.8 KB

Updated patch added! The missing files are now included.

tracipotocnik’s picture

Status: Needs work » Needs review
Bojhan’s picture

Can you add a few before/after screenshots?

yoroy’s picture

Thanks for working on this @tracipotocnik!

@Bojhan screenshot is in #10. Here's some more.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.0-alpha1 will be released the week of July 31, 2017, which means new developments and disruptive changes should now be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.0-alpha1 will be released the week of January 17, 2018, which means new developments and disruptive changes should now be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.7.x-dev

Drupal 8.6.0-alpha1 will be released the week of July 16, 2018, which means new developments and disruptive changes should now be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.7.x-dev » 8.8.x-dev

Drupal 8.7.0-alpha1 will be released the week of March 11, 2019, which means new developments and disruptive changes should now be targeted against the 8.8.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.0-alpha1 will be released the week of October 14th, 2019, which means new developments and disruptive changes should now be targeted against the 8.9.x-dev branch. (Any changes to 8.9.x will also be committed to 9.0.x in preparation for Drupal 9’s release, but some changes like significant feature additions will be deferred to 9.1.x.). For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.1.x-dev

Drupal 8.9.0-beta1 was released on March 20, 2020. 8.9.x is the final, long-term support (LTS) minor release of Drupal 8, which means new developments and disruptive changes should now be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

bandanasharma’s picture

StatusFileSize
new4.92 KB

Re-roll the patch.

Version: 9.1.x-dev » 9.2.x-dev

Drupal 9.1.0-alpha1 will be released the week of October 19, 2020, which means new developments and disruptive changes should now be targeted for the 9.2.x-dev branch. For more information see the Drupal 9 minor version schedule and the Allowed changes during the Drupal 9 release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Drupal 9.2.0-alpha1 will be released the week of May 3, 2021, which means new developments and disruptive changes should now be targeted for the 9.3.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

rinku jacob 13’s picture

StatusFileSize
new148.72 KB
new141.17 KB

Verified and tested updated patch #23
patch applied successfully. thanks @BandanaSharma

kiran.kadam911’s picture

StatusFileSize
new4.92 KB

Re-roll the patch 9.3.x. Kindly review.

Thanks!

chetanbharambe’s picture

Status: Needs review » Reviewed & tested by the community
StatusFileSize
new316.24 KB
new358.13 KB
new312.36 KB
new352.07 KB
new340.37 KB

Verified and tested patch #27.
Patch applied successfully and looks good to me.

Testing Steps:
# Goto: admin/content, admin/structure, admin/config
# Check the spacing between titles, tables, action buttons

Expected Results:
# User should see the accurate spacing between titles, tables, action buttons

Actual Results:
# User is not able to see the accurate spacing between titles, tables, action buttons

Can be a move to RTBC.

Bojhan’s picture

Nice work!

lauriii’s picture

Status: Reviewed & tested by the community » Needs work

The CI failed for #27.

ravi.shankar’s picture

Status: Needs work » Needs review
StatusFileSize
new4.92 KB
new788 bytes

Addressing comment #30.

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

Drupal 9.3.0-rc1 was released on November 26, 2021, which means new developments and disruptive changes should now be targeted for the 9.4.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.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.

Harish1688’s picture

StatusFileSize
new294.72 KB
new234.34 KB

Tested the patch (2487027-31.patch) with core version (9.5.x-dev and 9.4.x-dev) working fine, good for RTBC.

Aamir M’s picture

Assigned: Unassigned » Aamir M
Aamir M’s picture

Assigned: Aamir M » Unassigned
StatusFileSize
new105.01 KB
new92.04 KB
new76.4 KB
new72.43 KB
new259.86 KB

Verified and tested patch #31.
Patch applied successfully and looks good to me.

Testing Steps:
# Goto: admin/content, admin/structure, admin/structure/views
# Check the spacing between titles, tables and action buttons

Can be a move to RTBC.

Aamir M’s picture

Assigned: Unassigned » Aamir M
Aamir M’s picture

Assigned: Aamir M » Unassigned
Status: Needs review » Reviewed & tested by the community

As per my previous comment patch #31 was Verified and tested.
Can be moved to RTBC.

bnjmnm’s picture

Status: Reviewed & tested by the community » Needs work

Spotted some things to address.

  1. +++ b/core/themes/seven/css/components/details.css
    @@ -24,3 +24,7 @@
    +details {
    +  margin-top: 0;
    +  margin-bottom: 20px;
    +}
    

    There's a .seven-details class a few lines up that is already getting margin styles. The margin styles should probably be changed there, or at least removed since they're immediately overridden by this.

  2. +++ b/core/themes/seven/css/components/form.css
    @@ -57,7 +57,7 @@ fieldset:not(.fieldgroup) > legend {
    +  margin: 0 0 20px;
    

    I notice here and several other places that the top margin is being removed altogether. This is a pretty big change and I'm not sure it is necessary to achieve the goals of this issue since adjacent margins will collapse. If there's a good reason for this, it would be good to justify in the issue summary.

  3. +++ b/core/themes/seven/css/components/form.css
    @@ -73,9 +73,17 @@ td > .form-item:only-child {
    +.form-actions {
    +  margin-top: 20px;
    +  margin-bottom: 20px;
    +}
    

    There are some other .form-actions styles further down this file. It would be best to have this adjacent to that.

  4. +++ b/core/themes/seven/css/components/messages.css
    @@ -2,10 +2,10 @@
    +  margin: 0 8px 10px 0;
    

    The bottom margin is being set to 20px in LTR, I'm guessing that was intended here too?

  5. +++ b/core/themes/seven/css/components/tabs.css
    @@ -82,6 +82,9 @@ li.tabs__tab a {
    +.region-header .tabs.primary {
    

    There's no guarantee the page title block is directly above the primary tabs. If the top margin is removed, this could result in an above block being directly atop the tabs with no spacing.

akshayadhav’s picture

Assigned: Unassigned » akshayadhav
akshayadhav’s picture

Assigned: akshayadhav » Unassigned
Status: Needs work » Needs review
StatusFileSize
new327.41 KB
new597.7 KB
new581.22 KB
new578.29 KB
new571.3 KB
new2.5 KB
new5.01 KB

@bnjmnm
Corrected points mentioned by you.

Agreed with:

I notice here and several other places that the top margin is being removed altogether. This is a pretty big change and I'm not sure it is necessary to achieve the goals of this issue since adjacent margins will collapse. If there's a good reason for this, it would be good to justify in the issue summary.

So as per comment #10 replaced 0.75em as margin-top with 10px. There should be margin top.

Regarding point #3:

There are some other .form-actions styles further down this file. It would be best to have this adjacent to that.

The other styles for .form-actions are being used for narrow devices (max-width: 600px).
.form-actions styles

Regarding point #4:

The bottom margin is being set to 20px in LTR, I'm guessing that was intended here too?

Yes, that is required. And not only for LTR, it is required for RTL as well. So making that change too.
Please refer the attached screenshots for both LTR and RTL messages (before and after).

Regarding point #5:

There's no guarantee the page title block is directly above the primary tabs. If the top margin is removed, this could result in an above block being directly atop the tabs with no spacing.

I guess there is a probability of placing the Primary tabs block without any other block above it. We will need to check for such scenarios, then only we can conclude on it. So, for the time being keeping the margin: 0 for it.

ambikahirode’s picture

Patch in #41 working fine for me on local 9.5

Aamir M’s picture

Assigned: Unassigned » Aamir M
Aamir M’s picture

Assigned: Aamir M » Unassigned
Status: Needs review » Reviewed & tested by the community
StatusFileSize
new189.13 KB
new76.4 KB
new72.43 KB
new73.77 KB
new65.46 KB

Verified and tested patch #41 on Drupal 9.5.x-dev. Patch applied successfully and looks good to me.

Testing steps:
1. Goto admin/Appearance
2. Set Seven theme in the Administration theme (Scroll down and see)
3. Save configuration
4. Go to Structure or Content
5. Observe the spacing above the Heading
6. Apply the patch
7. Reload the page. Now observe the spacing is displaying properly (Note: Clear all caches if required)

Testing Result:
1. After applying the patch empty space above the header is reduced

Can be moved to RTBC

catch’s picture

Status: Reviewed & tested by the community » Postponed

Postponing on #3304285: Remove Seven from core, this should probably be moved to the contrib Seven issue queue once that issue has been committed.

longwave’s picture

Project: Drupal core » Seven
Version: 9.5.x-dev » 1.0.0-alpha1
Component: Seven theme » Code
Status: Postponed » Reviewed & tested by the community

The Seven theme has been removed from Drupal 10 core. I confirmed that this issue only affects Seven and no other themes included with Drupal core, so I am moving this to the contributed Seven project and marking RTBC again as per #44.

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

avpaderno’s picture

Version: 1.0.0-alpha1 » 1.0.x-dev
avpaderno’s picture

Status: Reviewed & tested by the community » Needs work
Issue tags: -Needs design +Needs reroll, +Needs merge request

The patches are for Drupal core.

avpaderno’s picture

Version: 1.0.x-dev » 2.0.x-dev
avpaderno’s picture

avpaderno’s picture

avpaderno’s picture

Assigned: Unassigned » avpaderno

avpaderno’s picture

Assigned: avpaderno » Unassigned
Status: Needs work » Needs review
Issue tags: -Needs reroll, -Needs merge request

avpaderno changed the visibility of the branch 2487027-fix-the-vertical-rhythm to hidden.

avpaderno’s picture

Status: Needs review » Fixed

Status: Fixed » Closed (fixed)

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