From 0289c4d0f9b325b7a8bbe6876638adc8086eab1c Mon Sep 17 00:00:00 2001 From: Kartikaya Gupta Date: Thu, 1 Oct 2020 15:19:09 +0000 Subject: [PATCH] Bug 1668466 - Fix broken links. r=sylvestre Differential Revision: https://phabricator.services.mozilla.com/D92071 --- gfx/docs/Silk.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/gfx/docs/Silk.rst b/gfx/docs/Silk.rst index ebb8d6d89207..45ec627a1e7c 100644 --- a/gfx/docs/Silk.rst +++ b/gfx/docs/Silk.rst @@ -210,7 +210,7 @@ touch events, and then dispatch the resampled touch event to APZ. Touch events on Firefox OS occur on a *Touch Input Thread* whereas they are processed by APZ on the *APZ Controller Thread*. We use `Google Android’s touch -resampling `__ +resampling `__ algorithm to resample touch events. Currently, we have a strict ordering between Composites and touch @@ -247,7 +247,7 @@ down `__. +`CompositorBridgeParent::Destroy `__. During this time, the *main thread* is blocked on the parent process. CompositorBridgeParent::RecvStop runs on the *Compositor thread* and cleans up some resources, including setting the @@ -269,7 +269,7 @@ destruction and the CompositorBridgeParent::DeferredDestroy releases a reference to the CompositorBridgeParent on the *Compositor Thread*. Finally, the CompositorBridgeParent itself is destroyed on the *main thread* once both references are gone due to explicit `main thread -destruction `__. +destruction `__. With the ``CompositorVsyncScheduler::Observer``, any accesses to the widget after nsBaseWidget::DestroyCompositor executes are invalid. Any