Make WordPress Core

Opened 4 years ago

Last modified 8 months ago

#50684 new defect (bug)

Font/font-size change on login screen

Reported by: superpoincare's profile superpoincare Owned by:
Milestone: Future Release Priority: normal
Severity: normal Version:
Component: Login and Registration Keywords: needs-design-feedback
Focuses: ui, css, administration Cc:

Description

On Windows 10, when a user logs in, the font and the font-size in the input boxes change.

To be more precise, the wrong font and font-size is initially displayed. Only after clicking, the correct font and font-size appear.

A recording:

https://i.imgur.com/siMssM6.gif

Change History (10)

#1 @SergeyBiryukov
4 years ago

  • Component changed from Administration to Login and Registration
  • Focuses ui css added

This ticket was mentioned in Slack in #core-css by ryelle. View the logs.


4 years ago

#3 @sabernhardt
4 years ago

That happens with logins other than WordPress; it's a Chrome Chromium issue. Correction: it's any Chromium-based browser (Chrome, Edge, Opera).
https://bugs.chromium.org/p/chromium/issues/detail?id=953689#c37

The font styles (font-family and font-size) are not honored and it falls back to the browser default:
font: 400 13.3333px Arial; (for me, on Windows)

There might be a way to work around that, but I haven't found it. (-webkit-autofill did not work for font styles.)

Last edited 4 years ago by sabernhardt (previous) (diff)

#4 @SergeyBiryukov
4 years ago

Just noting that the Chrome issue above is closed as WontFix, as the original change was a security fix:

This is due to a change, rogerm@ landed in M74. https://crrev.com/9e68c4db781b71e9ea772ab60d34c7f10e100b57, which is due to a security requirement that I cannot elaborate on, yet. Sorry, but I have to mark this as Won't fix.

https://bugs.chromium.org/p/chromium/issues/detail?id=953689#c10

This is closed as Won't Fix because allowing the website to style the font enables it to steal data that the user has not selected to share with the website via side channel attacks. We may need to change the entire interaction pattern but don't have anything ready, yet.

https://bugs.chromium.org/p/chromium/issues/detail?id=953689#c37

Last edited 4 years ago by SergeyBiryukov (previous) (diff)

This ticket was mentioned in Slack in #core-css by kirstyburgoine. View the logs.


4 years ago

#6 @garrett-eclipse
4 years ago

Hmm if we can't change it in Chrome I wonder if we just make that the baseline. Setting the style of the form to use that font/font-size so the text doesn't change when you start entering text.

This ticket was mentioned in Slack in #core-css by kirstyburgoine. View the logs.


3 years ago

#8 @kburgoine
3 years ago

  • Keywords needs-design-feedback added

Added the needs-design-feedback keyword as this probably needs a review to see if there is a design option to make this less jarring at all

#9 @rajinsharwar
8 months ago

  • Milestone changed from Awaiting Review to 6.4
  • Version 5.4.2 deleted

Putting this old ticket for 6.4, the issue does seem to be still replicable.

#10 @rajinsharwar
8 months ago

  • Milestone changed from 6.4 to Future Release

As per my understanding, we really cannot do much here, unless Chromium solves the issue with their auto-fill. I don't think this will be happening soon, so moving this back to Future Release.

Note: See TracTickets for help on using tickets.