Reland: "Use texture layer when displaying an Android view"#100990
Reland: "Use texture layer when displaying an Android view"#100990fluttergithubbot merged 4 commits intoflutter:masterfrom
Conversation
|
So this change is landing a new feature, modifying a test for that feature, and making that test non-blocking? Is the idea that that test would then be immediately worked on next to sort out the problem with it that this change introduces? If so, we should definitely have a high-priority issue for that, so that this PR can be backed out unless that problem can be sorted out relatively quickly because we have a branch cut coming up. |
|
This pull request is not suitable for automatic merging in its current state.
|
… view" (flutter#100934)" (flutter#100950)" This reverts commit 37d619d.
|
@jmagman, @CaseyHillers do you know if there's an issue with the mac pool? these tasks have been queued for >3h. |
There was quite a few PRs today, so capacity was limited (g/flutter-infra-alerts shows a few of these). The checks have run and passed |
|
got it. Thanks! |
…142399) After #100990, we should use `initExpensiveAndroidView` for Android Hybrid Composition mode instead of `initSurfaceAndroidView`. `initSurfaceAndroidView` attempts to use `TLHC` when possible. In cases where that is not supported, it falls back to using Hybrid Composition. flutter/engine#49414
Relands #100237
I wasn't able to reproduce (on neither emulator/physical device) the test failure that reverted this PR.
My only guess is that the button I added to the app under test pushed some other keyed buttons offscreen.
I'm adding
bringup: trueto the test.Change summary
There's a customer in g3 that uses WebRTC view. This view is a SurfaceView, and cannot use a texture layer.
Commit 2e915be adds a new factory
PlatformViewsService.initExpensiveAndroidViewthat can be used to allow SurfaceViews in a Flutter app.