Firefox does not synchronously update its surface on resize
Categories
(Core :: Widget: Gtk, defect)
Tracking
()
People
(Reporter: bjoern.daase, Unassigned)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
3.32 MB,
video/webm
|
Details |
User Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:74.0) Gecko/20100101 Firefox/74.0
Steps to reproduce:
This was raised in https://gitlab.gnome.org/GNOME/mutter/-/issues/977#note_752470 and Robert said, there is no Firefox bug yet. So here you go.
It affects (at least) Firefox 74 in combination with mutter 3.36:
You always get a one frame glitch occasionally visible when using tiling (super+up|down|left|right) or when unfullscreening a video. This has most likely to do with Firefox not synchronously updating it surface on resize (original problem is here: https://bugzilla.mozilla.org/show_bug.cgi?id=1609538#c7).
Actual results:
A one frame glitch where Firefox is rendered fullscreen when it should be windowed.
Expected results:
No glitches.
Comment hidden (obsolete) |
Comment hidden (obsolete) |
Comment hidden (obsolete) |
Comment 4•4 years ago
|
||
Please use Widget Gtk
and make it block bug 635134 - that should get Martin involved.
Updated•4 years ago
|
Comment 5•4 years ago
|
||
Can you create a screencast (video) of the issue?
Thanks.
Reporter | ||
Comment 6•4 years ago
|
||
Reporter | ||
Comment 7•4 years ago
|
||
There you go. It is a bit hard to see because it is only one frame (especially the glitch when resizing) but the (un-)fullscreen glitch is actually quite visible in the screencast.
Comment 8•4 years ago
|
||
Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is --
(Backlog,) indicating it has has not been previously triaged, the bug's Severity is being updated to --
(default, untriaged.)
Comment 9•4 years ago
|
||
Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is --
(Backlog,) indicating it has has not been previously triaged, the bug's Severity is being updated to --
(default, untriaged.)
Comment 10•4 years ago
|
||
Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is --
(Backlog,) indicating it has has not been previously triaged, the bug's Severity is being updated to --
(default, untriaged.)
Comment 11•4 years ago
|
||
The severity of these bugs was changed, mistakenly, from normal
to S3
.
Because these bugs have a priority of --
, indicating that they have not been previously triaged, these bugs should be changed to Severity of --
.
Comment 12•4 years ago
|
||
This is actually a duplicate of bug 1608617
Description
•