"Reset" doesn't reset font settings
Reported by
human.p...@gmail.com,
Feb 12 2017
|
||||
Issue description
UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.37 Safari/537.36
Steps to reproduce the problem:
1. Change any of the font settings in chrome://settings/fonts
2. Hit "reset" button in the settings.
What is the expected behavior?
The font settings should be reset.
What went wrong?
The font settings are not reset.
The only way you can reset it is go to the preference file and manually remove the "webkit":{"webprefs":{"fonts":{"sansserif":{"font_name"}},"uses_universal_detector":true}} part.
Did this work before? N/A
Chrome version: 57.0.2987.37 Channel: beta
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: Shockwave Flash 24.0 r0
Worth noting that even though user *can* manually change the fonts to default values, surely. But there is a big difference: if you never changed your font setting, it will automatically change when changing display language.
For example, if you're using English interface, the default sans-serif font is Arial. If you never changed it, and now you changed your interface language to Simplified Chinese, this setting (sans-serif font) will automatically changed to "SimSun (宋体)". But if you EVER changed that setting before, even if you changed it back to Arial, it will NOT change any more among your interface language.
So an ability to reset font settings are important.
It was reported in issue 584400 but wrongly marked as duplicate.
,
Feb 13 2017
Able to reproduce this issue on Windows 10, Ubuntu 14.04 and Mac 10.12.3 with chrome version #57.0.2987.37 and earlier version M35-35.0.1916.0 These are the steps followed. 1. Launched chrome and navigated to "chrome://settings/fonts" 2. Changed the font type and size 3. In "chrome://settings" page, clicked on the reset button. 4. restarted the chrome 5. Observed font settings values are not reset to their default values. Attaching the screencast for reference This is a non-regression issue and marking it as untriaged.
,
Feb 13 2017
,
May 30 2017
,
Aug 21
Archiving old bugs that haven't been actively assigned in over a year. If you feel this issue should still be addressed, feel free to reopen it or to file a new issue. Thanks! |
||||
►
Sign in to add a comment |
||||
Comment 1 by ajha@chromium.org
, Feb 13 2017