Open Bug 1396816 Opened 3 years ago Updated 2 years ago

[W10] Artifacts left behind when the Download manager's width is resized

Categories

(Core :: Graphics, defect, P2)

All
Windows 10
defect

Tracking

()

Tracking Status
firefox55 --- wontfix
firefox56 --- wontfix
firefox57 --- wontfix
firefox58 --- wontfix
firefox59 --- wontfix
firefox60 --- fix-optional

People

(Reporter: ciprian_georgiu, Unassigned, NeedInfo)

Details

(Keywords: regression, Whiteboard: [gfx-noted])

Attachments

(1 file)

Attached video issue - screencast.mp4
[Affected versions]:
- latest Nightly 57.0a1
- Beta 56.0b9
- RC 55.0.3

[Affected platforms]:
- Windows 10 x64

[Steps to reproduce]:
1. Launch Firefox.
2. Open Firefox's downloads manager. (Ctrl + J)
3. Change the width size of the download manager window.

[Expected result]:
- No artifacts are displayed while resizing the Download manager's width

[Actual result]:
- Artifacts are displayed while resizing the Download manager's width

[Regression range]:
- Last good revision: d29f84406483c721a13cf9a52936ecced0c5c98a
  First bad revision: c54c652af04c5a918610bc3d419250177a68b9f7
  Pushlog:
https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=d29f84406483c721a13cf9a52936ecced0c5c98a&tochange=c54c652af04c5a918610bc3d419250177a68b9f7

[Additional notes]:
- I was able to repro this on a a HiDPI monitor (Dell UHD-1 P2415Qb) and with different scaling levels e.g. 125%, 200%. It appears that this issue is still present if I Sign out and Sign in back in Windows 10. On Win 8.1 and Win 7 I'm not seeing this artifacts.
- on a low dpi monitor I cannot see this behavior
Has Regression Range: --- → yes
Has STR: --- → yes
This looks like  graphics bug to me, but I can't reproduce it on latest Nightly (Win10) on a Dell XPS 13. If we could narrow down further the regression range it would definitely help.
Component: Downloads Panel → Graphics
Product: Firefox → Core
Jeff, invalidation problem?
Flags: needinfo?(jmuizelaar)
Priority: -- → P2
Too late for a fix in 57 since we are a few days away from release.
Looks like this is on the graphics team's backlog at this point. Dropping this from regression triage.
You need to log in before you can comment on or make changes to this bug.