Closed Bug 890612 Opened 11 years ago Closed 11 years ago

FF v22 causes a larger image and causes probs, restored to v21 and OK

Categories

(Firefox :: Untriaged, defect)

21 Branch
x86
Windows 7
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 851268

People

(Reporter: dave.bailes, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; rv:21.0) Gecko/20100101 Firefox/21.0 (Beta/Release)
Build ID: 20130511120803

Steps to reproduce:

FF auto updated to v22


Actual results:

All windows contents appeared larger, some (e.g. Virgin/Gmail "Compose") contents too large for window and function could not be used.


Expected results:

Not the above. Restored Windows system back to date with FF v21 - all OK.
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
Downgrading to Firefox 21 is a poor option, as that version will no longer receive security updates for any vulnerabilities that may be found.

Firefox 22 now respects the Windows "dpi scaling" option (see discussion in bug 851268), which it previously failed to support for Web content. This does mean that if your system is configured for >100% scaling (in the Windows Display control panel), content in Firefox will be displayed larger than before. This is expected/correct behavior given a Windows scaling factor of >100%.

However, if you were previously used to viewing pages with a >100% zoom factor (within Firefox, either manually or applied automatically by an add-on), or if you had increased the browser's minimum font size to compensate for a high-pixel-density screen, you may now be seeing "scaling upon scaling", resulting in excessively large display. The first thing to try would be a fresh profile, to check whether local settings or add-ons are contributing to this.
I have no idea what "Windows scaling" is! This is a case where computer stuff does not accommodate the only just computer literate. I have loads of experience in using the things but will have to ask someone what the above means.

Can't you clever guys read the individual settings, warn the user there may be problems and how to fix them. I don't have time to study the more intricate stuff.
You need to log in before you can comment on or make changes to this bug.