Forcing fullscreen may choose wrong monitor on Win7
Categories
(Core :: Widget: Win32, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr60 | --- | unaffected |
| firefox64 | --- | unaffected |
| firefox65 | + | verified |
| firefox66 | + | verified |
People
(Reporter: agashlin, Assigned: agashlin)
References
Details
(Keywords: regression)
Attachments
(1 file)
|
47 bytes,
text/x-phabricator-request
|
RyanVM
:
approval-mozilla-beta+
|
Details | Review |
Updated•6 years ago
|
| Assignee | ||
Updated•6 years ago
|
| Assignee | ||
Comment 1•6 years ago
|
||
| Assignee | ||
Comment 2•6 years ago
|
||
Comment 4•6 years ago
|
||
| bugherder | ||
Comment 5•6 years ago
|
||
Please nominate this for Beta approval when you get a chance. Let's get QA looking at this too.
| Assignee | ||
Comment 6•6 years ago
|
||
Comment on attachment 9034051 [details]
Bug 1514501 - Fix screen selection and scaling for fullscreen
[Beta/Release Uplift Approval Request]
Feature/Bug causing the regression: Bug 1482920
User impact if declined: On Win7, with multiple monitors (might need at least 3) and dpi scaling, when Firefox goes fullscreen it will do so on the wrong monitor.
Is this code covered by automated tests?: Unknown
Has the fix been verified in Nightly?: Yes
Needs manual test from QE?: No
If yes, steps to reproduce:
List of other uplifts needed: None
Risk to taking this patch: Low
Why is the change risky/not risky? (and alternatives if risky): It is a focused change which directly addresses the oversight that caused the regression. I've checked the issue on Nightly, reproducible in 20190109092644, fixed in 20190110893854.
String changes made/needed:
Comment 7•6 years ago
|
||
Comment on attachment 9034051 [details]
Bug 1514501 - Fix screen selection and scaling for fullscreen
[Triage Comment]
Fixes Firefox going fullscreen on the wrong monitor for some users under certain circumstances. Approved for 65.0b11.
Comment 8•6 years ago
|
||
| bugherder uplift | ||
Comment 9•6 years ago
|
||
I have managed to reproduce this issue using Firefox 65.0b4 on Windows 7 32bit VM.
This issue is verified fixed using Firefox 66.0a1 (BuildId:20190114014511) and Firefox 65.0b11 (provided in comment 8) on Windows 7 32bit VM.
Description
•