Make WordPress Core

Opened 5 months ago

Last modified 3 weeks ago

#61667 new enhancement

The margins above and below the login form are not the same

Reported by: deeppatel8950's profile deeppatel8950 Owned by:
Milestone: 6.8 Priority: normal
Severity: minor Version: 3.8
Component: Login and Registration Keywords: needs-design-feedback has-patch
Focuses: ui, css Cc:

Description


Attachments (8)

Screenshot 2024-07-17 at 11.00.48 AM.png (251.4 KB) - added by deeppatel8950 5 months ago.
Screenshot 2024-07-17 at 11.01.03 AM.png (245.2 KB) - added by deeppatel8950 5 months ago.
61667.patch (409 bytes) - added by viralsampat 5 months ago.
I have checked above mentioned issue and I have resolved it and added patch. Also, I have attached screenshot after resolved this issue.
Screenshot 2024-07-17 at 6.35.21 PM.png (372.5 KB) - added by viralsampat 5 months ago.
After resolved:
Screenshot 2024-07-17 at 2.49.27 PM.png (158.1 KB) - added by priyank9033 5 months ago.
61667.diff (736 bytes) - added by vijaysinh9094 5 months ago.
logo margin issue fixed as per last discussion.
Screenshot 2024-07-18 112534.png (60.7 KB) - added by vijaysinh9094 5 months ago.
After making changes, the logo margin is reduce by 1px as per the last discussion.
61667.2.diff (367 bytes) - added by vijaysinh9094 5 months ago.
@sabernhardt I have updated the patch to change the bottom margin of the logo to 24 pixels to maintain consistency with other pixel-based measurements on the login page, which are typically in multiples of 4. The previous patch included a 25px bottom margin, but it was identified that this measurement did not align with the common practice on the login page. Additionally, the patch file 61667.diff was previously saved in UTF-16 encoding. I have recreated and saved the new patch file in UTF-8 encoding to ensure compatibility and consistency with the project requirements.

Download all attachments as: .zip

Change History (19)

#1 @audrasjb
5 months ago

  • Keywords reporter-feedback added

Hello, thank you for the report.

This was modified in purpose in #61013 to remove the extra bottom padding on the form.

Except for the different padding values –which is not really an issue–, what is the functional issue you wanted to report?

Thank you

#2 @audrasjb
5 months ago

Oh sorry it is not related to #61013, which is about (internal) paddings and not (external) margins :)

Let's reformulate my question then: Having a different margin at the bottom of an element may be useful to visually separate the element at the bottom. Do you think these different spacings between the element are a causing an issue?

#3 @priyank9033
5 months ago

@audrasjb I think there is a difference of 1px at the bottom of the logo. We can keep the top margin as it is on the form for UI purposes.

Last edited 5 months ago by priyank9033 (previous) (diff)

#4 @deeppatel8950
5 months ago

@audrasjb I think @priyank9033 is right. We can reduce the bottom margin of the logo by 1px and keep the top margin of the form as it is.

#5 @deeppatel8950
5 months ago

  • Keywords needs-patch added; reporter-feedback removed

@viralsampat
5 months ago

I have checked above mentioned issue and I have resolved it and added patch. Also, I have attached screenshot after resolved this issue.

#6 @deeppatel8950
5 months ago

  • Keywords needs-design-feedback added

@vijaysinh9094
5 months ago

logo margin issue fixed as per last discussion.

@vijaysinh9094
5 months ago

After making changes, the logo margin is reduce by 1px as per the last discussion.

#7 @sabernhardt
5 months ago

  • Keywords has-patch needs-refresh added; needs-patch removed
  • Milestone changed from Awaiting Review to 6.7
  • Severity changed from normal to minor
  • Summary changed from The top and bottom margins of the login form are not the same. to The margins above and below the login form are not the same
  • Type changed from defect (bug) to enhancement
  • Version changed from 6.6 to 3.8

I agree to change the logo's bottom margin to 24 pixels.

[26072] included both the 25px bottom margin on the logo link and 24px for the top margin on the #nav container, but most pixel-based measurements on the login page are in multiples of 4.

@vijaysinh9094 Your 61667.diff is saved in UTF-16. Could you re-create the patch using UTF-8? (If not, I could upload a patch.)

@vijaysinh9094
5 months ago

@sabernhardt I have updated the patch to change the bottom margin of the logo to 24 pixels to maintain consistency with other pixel-based measurements on the login page, which are typically in multiples of 4. The previous patch included a 25px bottom margin, but it was identified that this measurement did not align with the common practice on the login page. Additionally, the patch file 61667.diff was previously saved in UTF-16 encoding. I have recreated and saved the new patch file in UTF-8 encoding to ensure compatibility and consistency with the project requirements.

#8 @sabernhardt
5 months ago

  • Keywords needs-refresh removed

Thanks!

#9 @davidbaumwald
2 months ago

  • Milestone changed from 6.7 to 6.8

Seems like this is getting closer, but needs a bit more work.

With 6.7 Beta 1 releasing in a few hours, this is being moved to 6.8 given recent momentum towards a resolution.

If any committer feels the remaining work can be resolved in time for Beta 1 and wishes to assume ownership, feel free to update the milestone accordingly.

This ticket was mentioned in PR #7770 on WordPress/wordpress-develop by @im3dabasia1.


3 weeks ago
#10

### Trac Ticket
Trac ticket: https://core.trac.wordpress.org/ticket/61667

### Brief Description
This pull request addresses Trac Ticket #61667 by adjusting the margins around the login form for visual consistency. The margin above and below the form is now consistently set to 24px, and the margin below the logo has also been adjusted to 24px, as discussed in the Trac.

#11 @im3dabasia1
3 weeks ago

Hey @davidbaumwald

I've added a corresponding [PR](https://github.com/WordPress/wordpress-develop/pull/7770) for the requested changes. Let me know if the PR needs any further enhancements.

Note: See TracTickets for help on using tickets.