Bug 454059 - Generate hyperlinks in PDF output for HTML link elements. r=mstange,mattwoodrow Differential Revision: https://phabricator.services.mozilla.com/D114208

Bug 454059 - Add a LINK display-item type. r=mattwoodrow Differential Revision: https://phabricator.services.mozilla.com/D114207

Bug 1709452 - Do not store display list building rect in frames with continuations r=mattwoodrow Differential Revision: https://phabricator.services.mozilla.com/D114290

Bug 1710331 - Remove unused code in CompositorBridgeParent::RecvAdoptChild() r=gfx-reviewers,mattwoodrow Differential Revision: https://phabricator.services.mozilla.com/D114701

Bug 1708083. Schedule a paint when the presshell resolution changes. r=mattwoodrow Surprisingly nothing actually schedules a paint when the resolution changes. This probably wasn't a problem because when the resolution changes almost certainly something else is changing that causes a paint too (scroll position, display port, etc). We hit this in the test I wrote for bug 1706868. We double tap zoom in. In the last RequestContentRepaint from apz to content the only thing that changes is the resolution by a small amount. If he scroll offset or display port margins changed we'd ask for a paint, but evidently they do not. Content updates it's resolution, but since it does not generate a paint apz never gets notified about this, so it thinks content has a slightly different resolution. Then the test starts a double tap zoom out. When it notifies content of the new resolutions APZCCallbackHelper does nothing because of this line https://searchfox.org/mozilla-central/rev/4648b6ee31c2519b1753023e4f4853b14fdd16e5/gfx/layers/apz/util/APZCCallbackHelper.cpp#335 where it detects that the content resolution and what apz thinks is the content resolution differ by too much, so it thinks the request from apz is out of date and ignores it. Differential Revision: https://phabricator.services.mozilla.com/D113614

Bug 1706198 - Avoid source-to-dest-to-source conversions during clipping of blit rects. r=mattwoodrow The problem stems from the fact that to clip the dest rectangle to the source rectangle when there is scaling between them, we have to round at each step due to the fact we're working in integer coordinates. This causes us to nudge the coordinates in weird directions. To avoid this, this uses a slightly different approach where we essentially modify the existing clip rectangle functionality to factor in the texture bounds so that we don't have to do as many lossy conversions. Differential Revision: https://phabricator.services.mozilla.com/D112688

Bug 1705979 - Add support for nearest filtered scaled composites to SWGL. r=mattwoodrow Differential Revision: https://phabricator.services.mozilla.com/D112493

Bug 1704445: Take read lock before write lock when copying previous texture to new back buffer. r=mattwoodrow This is to try and prevent deadlocks between the compositor/renderer threads and the canvas threads. Differential Revision: https://phabricator.services.mozilla.com/D111853

Bug 1658924: Implement HTTPS-First and automatically fall back to http if secure top-level connection is not available r=necko-reviewers,JulianWels,mattwoodrow,dragana Differential Revision: https://phabricator.services.mozilla.com/D111686

Bug 1703724 - Don't set the color space on macOS HW decoded video. r=mattwoodrow It is already set by VideoCore to a profile with 1.9 gamma. This causes hw decoded video to have a different color profile than software decoded video which isn't ideal but matches what happens in Chrome. Differential Revision: https://phabricator.services.mozilla.com/D111218

Bug 1702530 - do not launch RDD process if XPCOM has started shutdown. r=mattwoodrow Differential Revision: https://phabricator.services.mozilla.com/D110982

Bug 1701292: Remove deleted subdirectory from layout/reftests/backgrounds/reftest.list. r=mattwoodrow Differential Revision: https://phabricator.services.mozilla.com/D109941

Bug 1701135 - Share ShaderProgramOGLs between CompositorOGLs during sw-wr + CompositorOGL r=mattwoodrow Differential Revision: https://phabricator.services.mozilla.com/D109856

Bug 1523500 - Introduce nsLayoutUtils::IsAncestorFrameCrossDocInProcess and use it to find an ASR for perspective display items. r=mattwoodrow Differential Revision: https://phabricator.services.mozilla.com/D109447

Bug 1699533: Push most uses of AutoSerializeWithMoz2D in canvas classes into D3D11TextureData. r=mattwoodrow This should ensure that we are more rigorous about always serializing when required. For example in this crash it appears the issue is that we are not using it when destroying the textures still held by the CanvasTranslator on its destruction. It also means that we can minimize the code that is serialized, which should reduce contention and possible deadlocks. This patch also ensures that we drop any other references to the texture's DrawTarget before dropping the texture, so that it can control the destruction of its DrawTarget including any locking. Differential Revision: https://phabricator.services.mozilla.com/D109771

Bug 1523500 - Introduce nsLayoutUtils::IsAncestorFrameCrossDocInProcess and use it to find an ASR for perspective display items. r=mattwoodrow Differential Revision: https://phabricator.services.mozilla.com/D109447

Bug 1700949 - Set pref gfx.webrender.fallback.software to false on Android r=mattwoodrow Support of fallback to sw-wr is not completed yet on Android. Differential Revision: https://phabricator.services.mozilla.com/D109831

Bug 1689156 - Bring the fast tab switch paint back r=mstange,mattwoodrow In bug 1669239, we removed the magic paint which would occur during tab switches, and instead we requested a tick. However, this approach didn't work well because tick was a heavy operation which did not only paints but also many other stuff, such as running requestAnimationFrame handlers, so it made the tab switches slower under certain conditions. So here we reverts the changes we made in bug 1669239. Differential Revision: https://phabricator.services.mozilla.com/D107858

Bug 1663757 - Part 2: Don't suspend webProgress on process switch, r=annyG,mattwoodrow Previously, we would need to suspend progress events from the previous BrowserParent, as otherwise we would receive STATE_STOP progress notifications from the previous browser when it is destroyed, which would throw off frontend code. With the new checks added by part 1, we will now catch these cases by detecting that the current window global has changed, and we can get rid of this explicit override. Differential Revision: https://phabricator.services.mozilla.com/D105557

Bug 1663757 - Part 1: Include BrowsingContext info in WebProgressData, r=mattwoodrow This change allows associating individual web progress events with which frame they originate from, rather than only recording the `isToplevel` information as we were before, which is necessary in order to use the OnLocationChange events from content to track the current URI on CanonicalBrowsingContext. Due to events in ContentChild being filtered through nsBrowserStatusFilter, some of the callbacks will never be passed nsIRequest or nsIWebProgress pointers, and this patch also simplifies them by removing information which is not necessary from the IPC message. Finally, this patch adds a number of checks to the relevant Recv callbacks in the parent process which help ensure that it does not accept web progress events from a content process which is no longer hosting the target BrowsingContext. This may allow for us to stop manually suspending web progress events on process switches, as these checks will handle this automatically based on the existing BrowsingContext and WindowContext objects. Differential Revision: https://phabricator.services.mozilla.com/D105556

Bug 1696325 - Handle StagingTexture allocation failure in RenderCompositorD3D11SWGL r=mattwoodrow Differential Revision: https://phabricator.services.mozilla.com/D107176

Bug 1695752 - Make RegisterThemeGeometry handle axis-aligned rectangles. r=mattwoodrow Differential Revision: https://phabricator.services.mozilla.com/D106828

Bug 1692957 - reject promise if RDD has been destroyed. r=mattwoodrow This could happen if RDD crashed right after it created, then `RDDProcessManager` would clean `mProcess` and `mRDDChild` before running the lambda. Depends on D106827 Differential Revision: https://phabricator.services.mozilla.com/D106837

Bug 1685666 - check RDDChild before creating content bridge. r=mattwoodrow As the process of creating content process is async, the RDD process might be shutdown before that (eg. crash). So we should check if RDD still exists first. Differential Revision: https://phabricator.services.mozilla.com/D106827

Bug 1682713 - Recreate the CVDisplayLink after display reconfigurations. r=mattwoodrow On M1 machines, the fix from bug 1422855 was not effective; stopping and starting the CVDisplayLink is not enough to cause it to switch to an active display. So we create a new display link, which will pick an active display. This patch is written to be minimum impact and easy to uplift. More cleanup is needed in the future. Differential Revision: https://phabricator.services.mozilla.com/D106744

Bug 1695581: Add #if for MOZ_FFVPX around StaticPrefs::media_rdd_ffvpx_enabled in AllDecodersAreRemote. r=mattwoodrow Differential Revision: https://phabricator.services.mozilla.com/D106754

Bug 1673342 - Add Support of software WebRender with CompositorOGL on Android and Linux r=mattwoodrow Differential Revision: https://phabricator.services.mozilla.com/D106234

Bug 1693541 - Improve uses of nsBaseHashtable and descendants and avoid multiple subsequent lookups in dom/html. r=mattwoodrow Differential Revision: https://phabricator.services.mozilla.com/D106112

Bug 1694822 - Fix return of RenderCompositorD3D11SWGL::DoCreateTile() r=mattwoodrow "return" was removed by mistake. Differential Revision: https://phabricator.services.mozilla.com/D106360

Bug 1692894 p2: Don't create devices for decoding when all decoders are remote. r=mattwoodrow Differential Revision: https://phabricator.services.mozilla.com/D105631

Bug 1526970 - Part 4: Check the frame for display items rather than DisplayItemData or WebRenderFallbackData in InvalidateFrame() r=mattwoodrow Depends on D106165 Differential Revision: https://phabricator.services.mozilla.com/D106166

Bug 1526970 - Part 3: Remove nsPaintedDisplayItem::mDisplayItemData r=mattwoodrow Depends on D106164 Differential Revision: https://phabricator.services.mozilla.com/D106165

Bug 1526970 - Part 2: Convert nsIFrame::mDisplayItemData to frame property r=mattwoodrow Depends on D104059 Differential Revision: https://phabricator.services.mozilla.com/D106164

Bug 1526970 - Part 1: Store the list of display items the frame has as a member variable instead of frame property r=mattwoodrow,emilio Differential Revision: https://phabricator.services.mozilla.com/D104059

Bug 1688096 - Part 2. Add flag to CompositorOptions to allow SW-WR on a per widget basis. r=mattwoodrow The pref gfx.webrender.software.unaccelerated-widget.allow may be used to allow software WebRender to be used with new windows/popups that have transparency on Windows. Otherwise they would fallback to basic layers. Similarly, the pref gfx.webrender.software.unaccelerated-widget.force may be used to force software WebRender for all windows that would fallback to basic layers. Differential Revision: https://phabricator.services.mozilla.com/D104855

Bug 1688096 - Part 1. Merge SW-WR and WR render texture host paths to allow mixed compositors. r=mattwoodrow Differential Revision: https://phabricator.services.mozilla.com/D104854

Bug 1690216 - Clarify that StartRemoteDrawingInRegion does not actually modify the region. r=mattwoodrow It caused us substantial confusion investigating this bug under the belief that StartRemoteDrawingInRegion may have been modifying the dirty region. None of our existing widget code anymore uses the API in this way, so it makes sense to just force this dirty region to be const so that we no longer support the assumption and alleviate confusion in the future about how our widget code actually behaves. Depends on D106246 Differential Revision: https://phabricator.services.mozilla.com/D106247

Bug 1690216 - Report whether to redraw on invalidation to WR. r=mattwoodrow This requires us to plumb CompositorCapabilities to support the extra field. This is complicated by the fact that since it is a Rust struct, it has no default constructor that can pass through to C++ via bindings, so every one of our RenderCompositors was forced to manually initialize fields. To get around this brittle footgun, instead the structure is initialized on the Rust side, and RenderCompositor's are encouraged to only change fields that actually diverge from the defaults as passed in via pointer. Finally, we can then do what we need to do, which is just to send the ForceRedraw message that needs to happen based on what we know about CompositorCapabilities. Differential Revision: https://phabricator.services.mozilla.com/D106246

Bug 1690216 - Report whether to redraw on invalidation to WR. r=mattwoodrow This requires us to plumb CompositorCapabilities to support the extra field. This is complicated by the fact that since it is a Rust struct, it has no default constructor that can pass through to C++ via bindings, so every one of our RenderCompositors was forced to manually initialize fields. To get around this brittle footgun, instead the structure is initialized on the Rust side, and RenderCompositor's are encouraged to only change fields that actually diverge from the defaults as passed in via pointer. Finally, we can then do what we need to do, which is just to send the ForceRedraw message that needs to happen based on what we know about CompositorCapabilities. Differential Revision: https://phabricator.services.mozilla.com/D106246

Bug 1677459 - Split platform independent part to RenderCompositorCompositorSWGL r=mattwoodrow The change is a preparation of Bug 1673342 Differential Revision: https://phabricator.services.mozilla.com/D99046

Bug 1677459 - Split platform independent part to RenderCompositorCompositorSWGL r=mattwoodrow The change is a preparation of Bug 1673342 Differential Revision: https://phabricator.services.mozilla.com/D99046

Bug 1422855 - Tickle the CVDisplayLink after display reconfigurations, to help it get unstuck. r=mattwoodrow This fixes a problem where the callback just wouldn't be called for the duration of about a minute after fast user switching. I'm hoping it'll also help with a similar problem after screen lock and after sleep (bug 1682713). The documentation for CVDisplayLinkStop says the following: > In macOS 10.4 and later, the display link thread is automatically stopped if > the user employs Fast User Switching. The display link is restarted when > switching back to the original user. This probably works for display links that were created before fast user switching. However, we sometimes create a new CVDisplayLink while our user is "in the background", and this new display link happily keeps running while we're in the background. Then, when switching back to the original user, *that's* when the display link is stopped. And then it eventually starts again. I'm not sure what causes it to re-start. Creating a CVDisplayLink while the machine is fast user switched to a different user is probably not a well-excercised codepath. Things might work more reliably if we keep reusing the same CVDisplayLink instance and just stop and start it as needed. But that's a more risky change that I don't want to uplift. Also, starting to listen for vsync while a different user is the "current" user is probably a mistake anyway. We should find out if there's a way to suspend compositing and drawing in that state. However, it seems that the window doesn't enter the occluded state during this time, because in that case we would de-activate the content docshell and not run requestAnimationFrame callbacks. But the profiler clearly shows rAF running during the switched-away time. I'm seeing the following display reconfiguration callbacks during fast user switching, 2077750265 being the display link's current display: ``` [1] DisplayReconfiguration for 2077750265: BeginConfiguration [2] DisplayReconfiguration for 1104977158: BeginConfiguration [3] DisplayReconfiguration for 2077750265: Remove Disabled [4] DisplayReconfiguration for 1104977158: Moved SetMain SetMode Add Enabled [5] DisplayReconfiguration for 1104977158: BeginConfiguration [6] DisplayReconfiguration for 2077750265: BeginConfiguration [7] DisplayReconfiguration for 1104977158: Remove Disabled DesktopShapeChanged [8] DisplayReconfiguration for 2077750265: Moved SetMain SetMode Add Enabled DesktopShapeChanged ``` With this patch, we restart the display link at notification 4 and 8. In the future, we should switch to per-monitor (or per-window) vsync rather than global vsync, and clean this whole situation up a little. Differential Revision: https://phabricator.services.mozilla.com/D105868

Bug 1688096 - Part 2. Add/use flag to CompositorOptions to allow SW-WR on a per widget basis. r=mattwoodrow The pref gfx.webrender.software.unaccelerated-widget.allow may be used to allow software WebRender to be used with new windows/popups that have transparency on Windows. Otherwise they would fallback to basic layers. Similarly, the pref gfx.webrender.software.unaccelerated-widget.force may be used to force software WebRender for all windows that would fallback to basic layers. Differential Revision: https://phabricator.services.mozilla.com/D104855

Bug 1688096 - Part 1. Merge SW-WR and WR render texture host paths to allow mixed compositors. r=mattwoodrow Differential Revision: https://phabricator.services.mozilla.com/D104854

Bug 1688096 - Part 2. Add/use flag to CompositorOptions to allow SW-WR on a per widget basis. r=mattwoodrow The pref gfx.webrender.software.unaccelerated-widget.allow may be used to allow software WebRender to be used with new windows/popups that have transparency on Windows. Otherwise they would fallback to basic layers. Similarly, the pref gfx.webrender.software.unaccelerated-widget.force may be used to force software WebRender for all windows that would fallback to basic layers. Differential Revision: https://phabricator.services.mozilla.com/D104855

Bug 1688096 - Part 1. Merge SW-WR and WR render texture host paths to allow mixed compositors. r=mattwoodrow Differential Revision: https://phabricator.services.mozilla.com/D104854

Bug 1690491 - Add Texture2D allocation failure handling to RenderCompositorD3D11SWGL r=mattwoodrow Texture2D allocation could fail by oom or device reset. Differential Revision: https://phabricator.services.mozilla.com/D105406

Bug 1693241 - Add gfxCriticalNote to RenderTextureHostSWGL::LockSWGLCompositeSurface() r=mattwoodrow It helps to understand Bug 1693208. Differential Revision: https://phabricator.services.mozilla.com/D105418

Bug 1693241 - Add gfxCriticalNote to RenderTextureHostSWGL::LockSWGLCompositeSurface() r=mattwoodrow It helps to understand Bug 1693208 . Differential Revision: https://phabricator.services.mozilla.com/D105418

Bug 1691895 - Make RenderCompositorSWGL work on android r=geckoview-reviewers,mattwoodrow,agi Partial present is not supported yet with RenderCompositorSWGL on Android. Differential Revision: https://phabricator.services.mozilla.com/D104654