Prepare for dynamically sized views - pt. 2 (#139079)
Towards https://github.com/flutter/flutter/issues/134501. Required to roll https://github.com/flutter/engine/pull/48090 into the framework. Two new subclasses of FlutterView were added recently for testing (in https://github.com/flutter/flutter/pull/138849) that I missed in my previous PR (https://github.com/flutter/flutter/pull/138565).
This commit is contained in:
parent
bf5d2b875f
commit
9147a1c1b8
@ -17,7 +17,7 @@ class FakeView extends TestFlutterView {
|
||||
final int viewId;
|
||||
|
||||
@override
|
||||
void render(Scene scene) {
|
||||
void render(Scene scene, {Size? size}) {
|
||||
// Do not render the scene in the engine. The engine only observes one
|
||||
// instance of FlutterView (the _view), and it is generally expected that
|
||||
// the framework will render no more than one `Scene` per frame.
|
||||
|
@ -17,7 +17,7 @@ class FakeView extends TestFlutterView {
|
||||
final int viewId;
|
||||
|
||||
@override
|
||||
void render(Scene scene) {
|
||||
void render(Scene scene, {Size? size}) {
|
||||
// Do not render the scene in the engine. The engine only observes one
|
||||
// instance of FlutterView (the _view), and it is generally expected that
|
||||
// the framework will render no more than one `Scene` per frame.
|
||||
|
Loading…
x
Reference in New Issue
Block a user