- May 31, 2022
-
-
Glenn Watson authored
Bug 1771561 - Fix incorrectly invalidating tiles with zero-sized backdrop filters r=gfx-reviewers,lsalzman a=pascalc Differential Revision: https://phabricator.services.mozilla.com/D147710
-
Glenn Watson authored
Bug 1771556 - Handle backdrop capture failing clip check when sub-graph is visible r=gfx-reviewers,lsalzman a=pascalc This can happen when there is a long nested chain of backdrop-filters and float inaccuracies cause the final capture primitive to be culled. Differential Revision: https://phabricator.services.mozilla.com/D147704
-
- May 27, 2022
-
-
Butkovits Atila authored
-
Lee Salzman authored
Differential Revision: https://phabricator.services.mozilla.com/D147520
-
- May 26, 2022
-
-
Glenn Watson authored
Bug 1771293 - Handle backdrop-filter chains that are culled due to being invisible r=gfx-reviewers,lsalzman Differential Revision: https://phabricator.services.mozilla.com/D147460
-
Glenn Watson authored
Differential Revision: https://phabricator.services.mozilla.com/D147454
-
- May 25, 2022
-
-
Glenn Watson authored
This was fixed by the patch in 1769963, so this patch just adds a crash test to ensure we don't regress in future. Differential Revision: https://phabricator.services.mozilla.com/D147223
-
Marian-Vasile Laza authored
Backed out changeset e216b94199d5 (bug 1770045) relies on the fix in the backed out patch - Bug 1769963. CLOSED TREE a=backout
-
Marian-Vasile Laza authored
Backed out changeset e216b94199d5 (bug 1770045) relies on the fix in the backed out patch - Bug 1769963. CLOSED TREE
-
- May 24, 2022
-
-
Glenn Watson authored
This was fixed by the patch in 1769963, so this patch just adds a crash test to ensure we don't regress in future. Differential Revision: https://phabricator.services.mozilla.com/D147223
-
- May 19, 2022
-
-
Joel Maher authored
Differential Revision: https://phabricator.services.mozilla.com/D146633
-
- May 16, 2022
-
-
Jonathan Kew authored
Depends on D145902 Differential Revision: https://phabricator.services.mozilla.com/D145903
-
- May 06, 2022
-
-
Emilio Cobos Álvarez authored
Bug 1767172 - Remove custom screen info handling from GfxInfo, use ScreenManager for that. r=jrmuizel,handyman,stransky This removes a bunch of custom code from GfxInfo to obtain screen information, and instead collects that screen information in ScreenManager. This, apart of removing duplicated code, has the extra benefit of reporting multi-monitor information on GTK (and potentially in the future reporting scale and refresh rate properly as well, I've kept the telemetry as it was on that regard). Differential Revision: https://phabricator.services.mozilla.com/D145178
-
Cosmin Sabou authored
Backed out changeset b2bea8e0b400 (bug 1767172) for causing startup crashes (Bug 1768260). a=backout
-
Glenn Watson authored
Bug 1765862 - Skip backdrop-filter if `nsIFrame` reports not visible for painting r=gfx-reviewers,lsalzman Differential Revision: https://phabricator.services.mozilla.com/D145526
-
- May 05, 2022
-
-
Emilio Cobos Álvarez authored
Bug 1767172 - Remove custom screen info handling from GfxInfo, use ScreenManager for that. r=jrmuizel,handyman,stransky This removes a bunch of custom code from GfxInfo to obtain screen information, and instead collects that screen information in ScreenManager. This, apart of removing duplicated code, has the extra benefit of reporting multi-monitor information on GTK (and potentially in the future reporting scale and refresh rate properly as well, I've kept the telemetry as it was on that regard). Differential Revision: https://phabricator.services.mozilla.com/D145178
-
Markus Stange authored
Bug 1765399 - Invert the relationship between VsyncSource and VsyncDispatcher: The VsyncDispatcher now owns the source. r=smaug This makes vsync source swapping much more natural. The VsyncSource now only has a reference to the VsyncDispatcher for the duration during which the dispatcher is listening to vsync. Whenever the dispatcher is not listening to vsync, the source has no reference to the dispatcher and there is no cycle. This patch also adds the ability to register multiple dispatchers with the same source. This ability is not used yet; a vsync source always has zero or one dispatchers at the moment. It is in preparation for a future patch where there will be one dispatcher per widget. Furthermore, nothing uses gfxPlatform::GetGlobalVsync anymore, so it is removed. Differential Revision: https://phabricator.services.mozilla.com/D144375
-
Markus Stange authored
Bug 1765399 - Rename Get/CreateHardwareVsync to GetGlobalVsync, CreateGlobalHardwareVsync and CreateSoftwareVsync. r=smaug This draws a clearer line between hardware vsync and software vsync. Differential Revision: https://phabricator.services.mozilla.com/D144373
-
Markus Stange authored
Bug 1765399 - Register CompositorVsyncDispatcher with VsyncDispatcher instead of directly with the VsyncSource. r=smaug This makes it so that the VsyncSource doesn't need to keep track of the compositor vsync dispatchers. And the moving-between-sources logic needs to be handled only for the VsyncDispatcher. Once we have one VsyncDispatcher per window, we can probably eliminate CompositorVsyncDispatcher. Differential Revision: https://phabricator.services.mozilla.com/D144366
-
Markus Stange authored
RefreshTimerVsyncDispatcher manages a lot more than just the RefreshDriverVsyncTimer these days. Differential Revision: https://phabricator.services.mozilla.com/D144363
-
- May 04, 2022
-
-
Marian-Vasile Laza authored
Backed out changeset 8ff5e213e351 (bug 1765399) Backed out changeset bd164f5cc8b3 (bug 1765399) Backed out changeset 939b577eee05 (bug 1765399) Backed out changeset ee00e3583f42 (bug 1765399) Backed out changeset e5001537e536 (bug 1765399) Backed out changeset d5a4004a2955 (bug 1765399) Backed out changeset d3c1f6c420e3 (bug 1765399) Backed out changeset d21fca656853 (bug 1765399) Backed out changeset 5e5a29a99c9e (bug 1765399) Backed out changeset ce326de1e107 (bug 1765399) Backed out changeset 3890e83660b0 (bug 1765399) Backed out changeset 2f3ceca7aefe (bug 1765399) Backed out changeset 40c47c498858 (bug 1765399) Backed out changeset 3a3a2aa6de9b (bug 1765399) Backed out changeset 4a30a4b3d30d (bug 1765399) Backed out changeset a9115d9d648e (bug 1765399)
-
Markus Stange authored
Bug 1765399 - Invert the relationship between VsyncSource and VsyncDispatcher: The VsyncDispatcher now owns the source. r=smaug This makes vsync source swapping much more natural. The VsyncSource now only has a reference to the VsyncDispatcher for the duration during which the dispatcher is listening to vsync. Whenever the dispatcher is not listening to vsync, the source has no reference to the dispatcher and there is no cycle. This patch also adds the ability to register multiple dispatchers with the same source. This ability is not used yet; a vsync source always has zero or one dispatchers at the moment. It is in preparation for a future patch where there will be one dispatcher per widget. Furthermore, nothing uses gfxPlatform::GetGlobalVsync anymore, so it is removed. Differential Revision: https://phabricator.services.mozilla.com/D144375
-
Markus Stange authored
Bug 1765399 - Rename Get/CreateHardwareVsync to GetGlobalVsync, CreateGlobalHardwareVsync and CreateSoftwareVsync. r=smaug This draws a clearer line between hardware vsync and software vsync. Differential Revision: https://phabricator.services.mozilla.com/D144373
-
Markus Stange authored
Bug 1765399 - Register CompositorVsyncDispatcher with VsyncDispatcher instead of directly with the VsyncSource. r=smaug This makes it so that the VsyncSource doesn't need to keep track of the compositor vsync dispatchers. And the moving-between-sources logic needs to be handled only for the VsyncDispatcher. Once we have one VsyncDispatcher per window, we can probably eliminate CompositorVsyncDispatcher. Differential Revision: https://phabricator.services.mozilla.com/D144366
-
Markus Stange authored
RefreshTimerVsyncDispatcher manages a lot more than just the RefreshDriverVsyncTimer these days. Differential Revision: https://phabricator.services.mozilla.com/D144363
-
Markus Stange authored
Nobody was checking the return value anywhere. Differential Revision: https://phabricator.services.mozilla.com/D144360
-
- May 03, 2022
-
-
Glenn Watson authored
Differential Revision: https://phabricator.services.mozilla.com/D145047
-
- May 02, 2022
-
-
Chris Martin authored
This member is no longer used on Windows, and having it in the base class doesn't provide a real abstraction anyway since the child classes will break if anything about it is changed. Differential Revision: https://phabricator.services.mozilla.com/D145132
-
- Apr 14, 2022
-
-
Florian Quèze authored
Bug 1764812 - Add a test ensuring vsync is disabled after tearing off a tab that has compositor animations, r=hiro. Differential Revision: https://phabricator.services.mozilla.com/D143748
-
- Apr 06, 2022
-
-
Lee Salzman authored
Differential Revision: https://phabricator.services.mozilla.com/D143067
-
- Mar 30, 2022
-
-
Glenn Watson authored
In these cases the combined local clip rect may be in reflected local space. Map them to true raster space and then unmap them back to the new local space to correct this. Differential Revision: https://phabricator.services.mozilla.com/D142430
-
donal meehan authored
-
Glenn Watson authored
Bug 1761460 - Fix local space clip rects on snapped surfaces with reflections r=gfx-reviewers,nical a=dmeehan In these cases the combined local clip rect may be in reflected local space. Map them to true raster space and then unmap them back to the new local space to correct this. Differential Revision: https://phabricator.services.mozilla.com/D142430
-
- Mar 28, 2022
-
-
Lee Salzman authored
Differential Revision: https://phabricator.services.mozilla.com/D142175
-
- Mar 16, 2022
-
-
Randell Jesup authored
Differential Revision: https://phabricator.services.mozilla.com/D140849
-
Noemi Erli authored
-
Randell Jesup authored
Differential Revision: https://phabricator.services.mozilla.com/D140849
-
Butkovits Atila authored
-
Randell Jesup authored
Differential Revision: https://phabricator.services.mozilla.com/D140849
-
- Mar 15, 2022
-
-
Markus Stange authored
Every `VsyncSource` currently only has a single `Display` associated with it. This means that we're not making use of the `Display` abstraction at all. This patch gets rid of `Display` by merging it into `VsyncSource`. Originally, the intention of the `Display` abstraction was to use it for per-monitor vsync. There would be one software `VsyncSource` and one hardware `VsyncSource`, and the hardware `VsyncSource` would have one `Display` per screen. But in reality, things have played out differently: The only platform with per-monitor vsync is currently Linux Wayland, which has per-**widget** vsync. And it has chosen to have one `VsyncSource` per widget, with a single `Display` each. For the macOS implementation of per-monitor vsync, I think it also makes sense to have one `VsyncSource` per screen. We already need to handle switching between VsyncSources, for switching between software and hardware vsync, if the pref `layout.frame_rate` is changed. So we might as well reuse that same switching capability for switching between screens, when a window moves between screens or when a tab moves between windows on different screens. Differential Revision: https://phabricator.services.mozilla.com/D140891
-