You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Inlining a SurfaceView in a PlatformView in a Flutter hierarchy should have an automated test #100669
In this specific issue, SurfaceView is embedded in a Flutter app.
SurfaceViews can't be drawn to a Canvas for the purpose of detecting what and where that view is rendered.
changed the title [-]Inlining a PlatformView in a Flutter hierarchy should have an automated test[/-][+]Inlining a SurfaceView in a PlatformView in a Flutter hierarchy should have an automated test[/+]on Mar 24, 2022
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.
Activity
blasten commentedon Mar 24, 2022
In this specific issue, SurfaceView is embedded in a Flutter app.
SurfaceViews can't be drawn to a Canvas for the purpose of detecting what and where that view is rendered.
https://github.com/flutter/flutter/tree/master/packages/integration_test#screenshots should be able to help here.
blasten commentedon Mar 24, 2022
offline conversation with jreck: this needs to use
UiAutomation#takeScreenshot(), and remove the status/navigation bars[-]Inlining a PlatformView in a Flutter hierarchy should have an automated test[/-][+]Inlining a SurfaceView in a PlatformView in a Flutter hierarchy should have an automated test[/+]xster commentedon Mar 24, 2022
Understood. Thanks. I was wondering, since we seem to have a bunch of platform view tests in the engine already.
blasten commentedon Mar 24, 2022
Closing in favor of #97853. That issue is tracking missing integration tests.
github-actions commentedon Apr 7, 2022
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.