Closed Bug 643750 Opened 14 years ago Closed 11 years ago

The size of default fonts should follow the OS setting (for accessibility)

Categories

(Core :: Layout: Text and Fonts, defect)

1.9.2 Branch
x86
All
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 844604

People

(Reporter: liujuny, Unassigned)

Details

(Keywords: access)

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.15) Gecko/20110303 Firefox/3.6.15 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.15) Gecko/20110303 Firefox/3.6.1 When user enlarge the system default font in OS setting, e.g. Windows 7 control panel->Control Panel ->Appearance and Personalization -> Display -> use Larger 150% fonts, user is expecting that all applications including Firefox/Xulrunner also enlarge the font size. But Firefox/Xulrunner also keep default font size. I have to say the MS IE behave a bit better at this point. I understand that user can use Ctrl++/- to zoom manually. But it will be better to make that happen automatically. Reproducible: Always Steps to Reproduce: 1.Change the OS font size to 150%, at control panel->Control Panel ->Appearance and Personalization -> Display -> use Larger 150% fonts 2. Open firefox to browser to any page with fonts, and check if any change at font size Actual Results: Font in page should be enlarged with 150%, as user set in OS Expected Results: Expecting the fonts will be enlarged 150%
Version: unspecified → 1.9.2 Branch
Summary: The sizing of default fonts should follow the OS setting (for accessibility) → The size of default fonts should follow the OS setting (for accessibility)
Whiteboard: DUPEME
Keywords: access
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
Whiteboard: DUPEME
Is that really what this is a duplicate of?
Yes; Win7 deals with high-pixel-density displays by altering the default value for font size (100%, 125%, 150%, ...) as exposed in the Display control panel, so this is talking about respecting the same system setting that bug 844604 was about -- whether it's expressed in terms of hi-dpi support or a11y needs, it's the same thing.
You need to log in before you can comment on or make changes to this bug.