Closed Bug 844857 Opened 12 years ago Closed 12 years ago

new window that should be centered on screen (e.g. "Checking Add-on Compatibility" dialog) appears in the lower right corner on HiDPI displays

Categories

(Core :: Widget: Win32, defect)

All
Windows 7
defect
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: edwardsgreg, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: fixed by bug 824386)

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:20.0) Gecko/20130219 Firefox/20.0 Build ID: 20130219042021 Steps to reproduce: You will need to have multiple installs of Firefox at different versions or install a major version update. Set Windows DPI to something high like 150 or 200% Set the layout.css.devPixelsPerPx value to -1.0 Close Firefox Run a different version than the one you were running. (needs to be at least version 18 or so to support getDefaultScale) Actual results: Observe that the Check Add-on Compatability dialog is in the lower right corner of the screen. Expected results: It should be in the middle of the screen.
Blocks: win-hidpi
Hardware: x86_64 → All
Status: UNCONFIRMED → NEW
Component: Untriaged → Widget: Win32
Ever confirmed: true
Product: Firefox → Core
Version: 20 Branch → Trunk
See bug 844846 for another example of this issue.
Summary: Checking Add-on Compatability dialog is in the lower right corner on HiDPI displays → new window that should be centered on screen (e.g. "Checking Add-on Compatibility" dialog) appears in the lower right corner on HiDPI displays
It doesn't affect all windows. Options and Downloads, for instance, are not affected.
I believe the patch for bug 824386 (just pushed to inbound) will fix this; let's re-test once that is in Nightly.
AFAICT, this is indeed fixed (by the patch in bug 824386). Greg, if you still see this problem, please re-open the bug and give details - thanks.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Works for me since bug 824386 landed.
Depends on: 824386
Whiteboard: fixed by bug 824386
You need to log in before you can comment on or make changes to this bug.