Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at
Bug 1745361 - [firefox-wayland] Visual artifacts when quickly snapping
Summary: [firefox-wayland] Visual artifacts when quickly snapping
Alias: None
Product: Fedora
Classification: Fedora
Component: firefox
Version: 30
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
Depends On:
Blocks: ffwayland
TreeView+ depends on / blocked
Reported: 2019-08-25 19:39 UTC by Bryant Zepeda
Modified: 2019-09-10 08:35 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2019-09-10 08:35:15 UTC
Type: Bug

Attachments (Terms of Use)

Description Bryant Zepeda 2019-08-25 19:39:56 UTC
+++ This bug was initially created as a clone of Bug #1583539 +++

Description of problem:
Visual noise when quickly snapping to edges or going fullscreen. Dark boxes, lines/tears of visual artifacts, and pink lines are most often seen when done.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Snap a firefox-wayland window to left or right edge. Note: Let go of the mouse as dragging a window, without declaring the position, to the left or right won't work as much.
2. Incredibly quickly snap the window to the opposite direction.
3. Going fullscreen (F11) also reproduces the same effect when done enough times.

Actual results:
Weird visual artifacts/noise appear on the window where it was formerly positioned at.

Expected results:
Non-Wayland Firefox does not have this strange effect. It should be a smooth visual transition.

Additional info:
Kernel driver in use: radeon
Kernel modules: radeon, amdgpu

Comment 1 Martin Stransky 2019-09-10 08:35:15 UTC
This should be already fixed ans also next round of patches goes out in

Note You need to log in before you can comment on or make changes to this bug.