Closed Bug 824386 Opened 13 years ago Closed 13 years ago

Fullscreen elements are larger than the dimensions of the display on high DPI displays

Categories

(Core :: Widget, defect)

x86_64
Windows 8
defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla22
Tracking Status
firefox22 - ---

People

(Reporter: josh.tumath+bugzilla, Assigned: jfkthame)

References

(Blocks 1 open bug)

Details

Attachments

(2 files)

User Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:20.0) Gecko/20121223 Firefox/20.0 Build ID: 20121223030832 Steps to reproduce: 1. In the Control Panel, set the DPI of the desktop to 150%. 2. Enable the HTML5 video player on YouTube 3. Open a YouTube video that uses the HTML5 video player and open it in fullscreen Actual results: The dimensions of the fullscreen element are about 30px than the actual size of the display, so the controls at the bottom of the YouTube video player are slightly cut off. Expected results: The fullscreen element should be the same dimensions as the resolution of the display.
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:20.0) Gecko/20130114 Firefox/20.0 I can replicate on Windows 7 with 200% DPI using the built-in fullscreen option in the main menu. It affects all pages, and the most notable effect is the scrollbar on the right edge is cut off. My devPixelsPerPx is manually set to -1.0. This should block Bug 820679.
Blocks: win-hidpi
Component: Layout → Widget: Win32
I also notice that when the window is restored from full-screen to "normal", it does not return to the correct original size. I suspect this is an aspect of the same underlying problem with handling the window dimensions when scaling is in effect.
Status: UNCONFIRMED → NEW
Ever confirmed: true
I see this also using 125% (120DPI). F11 full zoom extends to my second monitor about 25%. Also various menus opened in Fx and initially moved to my second monitor will always open about 1/4 of the way from the left margin. View Page Info does this as well as other things.
Attached image screenshot —
This should probably track since it's not just visual polish.
Just wanted to add that the problem I have with menus and windows aligning themselves on my second monitor 25% from the left side happens no matter what window size Fx is in. It's not limited to full screen mode (F11).
(In reply to Gary [:streetwolf] from comment #6) > Just wanted to add that the problem I have with menus and windows aligning > themselves on my second monitor 25% from the left side happens no matter > what window size Fx is in. It's not limited to full screen mode (F11). Please file a new bug blocking bug win-hidpi with a screen shot. This bug is specific to dom fullscreen video controls. If we can get individual bugs filed like this one on each individual problem we'll have much better luck finding owners who can fix the fallout.
Component: Widget: Win32 → DOM
Jim... is there one place to find all the reported bugs due to win-hidpi? I have issues with the way the chrome looks and blurry graphics in chrome and content. I recall reading that these are already being worked on.
Hmm... I cannot reproduce this. Maybe it's a layout issue rather than a fullscreen issue though.
(In reply to Gary [:streetwolf] from comment #9) > Jim... is there one place to find all the reported bugs due to win-hidpi? I > have issues with the way the chrome looks and blurry graphics in chrome and > content. I recall reading that these are already being worked on. The parent of this bug - bug 824386.
(In reply to Chris Pearce (:cpearce) from comment #10) > Hmm... I cannot reproduce this. Maybe it's a layout issue rather than a > fullscreen issue though. My str: 1) on the surface pro, open nightly on the desktop 2) visit http://www.w3.org/2010/05/video/mediaevents.html 3) click the fullscreen button on the bottom right
(In reply to Jim Mathies [:jimm] from comment #11) > (In reply to Gary [:streetwolf] from comment #9) > > Jim... is there one place to find all the reported bugs due to win-hidpi? I > > have issues with the way the chrome looks and blurry graphics in chrome and > > content. I recall reading that these are already being worked on. > > The parent of this bug - bug 824386. sorry - copy paste error - bug 820679
(In reply to Jim Mathies [:jimm] from comment #12) > (In reply to Chris Pearce (:cpearce) from comment #10) > > Hmm... I cannot reproduce this. Maybe it's a layout issue rather than a > > fullscreen issue though. > > My str: > > 1) on the surface pro, open nightly on the desktop > 2) visit http://www.w3.org/2010/05/video/mediaevents.html > 3) click the fullscreen button on the bottom right Ah, I was using Nightly from Feb 28, I updated to today's (17 Mar) and I can now reproduce the bug on my Surface Pro. So this must be a recent regression, sometime between 2013-02-28 and 2013-03-17.
It will have been triggered by bug 844604 (landed 2013-03-14), where we enabled scaling based on the Windows resolution setting. (My guess is that we're working with the physical pixel dimensions of the screen, but sizing the window using logical coordinates, or something like that - haven't tried to dig in properly yet.)
(In reply to Jim Mathies [:jimm] from comment #12) > (In reply to Chris Pearce (:cpearce) from comment #10) > > Hmm... I cannot reproduce this. Maybe it's a layout issue rather than a > > fullscreen issue though. > > My str: > > 1) on the surface pro, open nightly on the desktop > 2) visit http://www.w3.org/2010/05/video/mediaevents.html > 3) click the fullscreen button on the bottom right When I do this I get what I describe in my bug report regarding full screen mode. https://bugzilla.mozilla.org/show_bug.cgi?id=851952
From our read, bug 820679 hasn't been resolved yet. No need to track until there's actually a functional regression in 22.
Actually, at this point there -is- a functional regression in 22 as a result of bug 844604, as per comments 14 and 15. I'm expecting to have a patch ready for this shortly, but if for some reason that proves problematic, I think it would be sufficient reason to hold 844604 back for a cycle.
Blocks: 844604
This should also fix the issues with incorrectly centered windows (bug 844857) and failing to constrain restored windows to the screen size (bug 852371).
Assignee: nobody → jfkthame
Attachment #726569 - Flags: review?(jmathies)
Component: DOM → Widget
Comment on attachment 726569 [details] [diff] [review] patch, account for logical dpi in nsScreenWin Review of attachment 726569 [details] [diff] [review]: ----------------------------------------------------------------- ::: widget/windows/nsScreenWin.cpp @@ +93,5 @@ > + int32_t *outWidth, int32_t *outHeight) > +{ > + int32_t left, top, width, height; > + nsresult rv = GetRect(&left, &top, &width, &height); > + if (NS_SUCCEEDED(rv)) { nit - I'd prefer if (NS_FAILED(rv)) return rv; ... return NS_OK;
Attachment #726569 - Flags: review?(jmathies) → review+
Target Milestone: --- → mozilla22
What are the chances that your patch will also fix Bug 818927? (seems to involve absolute mouse positions -> css pixels)
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Blocks: 844857
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: