Drive SurfaceView visibility on renderthread
In some scenarios, a SurfaceView: 1. May be moved offscreen by an app, such as through a ViewPager2 2. Have its RenderNode removed from the draw tree 3. The SurfaceView is remade visible on the UI thread In this case, the view position is offscreen, but the SurfaceControl position is at (0, 0). If there happens to be another SurfaceView at (0, 0), then this causes an accidental overlap. To avoid this, visibility should be fully driven by RenderNode position callbacks. Bug: 269113414 Test: Test app with ViewPager2 Change-Id: Ia0abd56fe4be8b669d39864c5fc82e941fb3be8e
Loading
Please register or sign in to comment