Bug 405331 - KDE Neon Dev: Password not centered in Login Screen
Summary: KDE Neon Dev: Password not centered in Login Screen
Status: RESOLVED DUPLICATE of bug 399155
Alias: None
Product: plasma-integration
Classification: Plasma
Component: general (show other bugs)
Version: master
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-03-10 22:20 UTC by guimarcalsilva
Modified: 2019-03-31 10:18 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Login screen - password not centered (54.04 KB, image/jpeg)
2019-03-10 22:20 UTC, guimarcalsilva
Details

Note You need to log in before you can comment on or make changes to this bug.
Description guimarcalsilva 2019-03-10 22:20:33 UTC
Created attachment 118703 [details]
Login screen - password not centered

SUMMARY


STEPS TO REPRODUCE
1. Go to Login Screen
2. Enter password

OBSERVED RESULT

The text is not vertically centered on the text field (see attached screenshot)

EXPECTED RESULT

The text should be in the middle of the text field (vertically)

SOFTWARE/OS VERSIONS
Operating System: KDE neon Developer Edition
KDE Plasma Version: 5.15.80
KDE Frameworks Version: 5.56.0
Qt Version: 5.12.0
Kernel Version: 4.18.0-16-generic
OS Type: 64-bit
Comment 1 Patrick Silva 2019-03-11 02:08:06 UTC
known issue mentioned in Nate's blog
https://pointieststick.com/2019/03/10/this-week-in-usability-productivity-part-61/
Comment 2 Nate Graham 2019-03-16 23:48:55 UTC
Yeah.

If you look closely, the bullets were never vertically centered before, but now it's more noticeable as a side effect of fixing the bug that made the password field jump in height when you started typing.

This is on;y a problem on Neon because Neon uses a fontconfig file that falls back to the Noto Symbols font to get the bullet chatacter, which happens to be taller than Noto Sans. The solution here is to use a different character for the bullet.
Comment 3 guimarcalsilva 2019-03-18 23:57:23 UTC
This bug seems to have been fixed in the last update (17th of march).
Comment 4 Christoph Feck 2019-03-31 10:18:00 UTC

*** This bug has been marked as a duplicate of bug 399155 ***