1. 18 Oct, 2023 1 commit
    • pdblasi-google's avatar
      Adds API for performing semantics actions in tests (#132598) · 52a1a318
      pdblasi-google authored
      * Added `performAction` to `SemanticsController` as well as specific methods for specific actions
      * Added a `scrollable` finder to `find.semantics` as a convenience method for `findAny(<all scrollable actions>)`
      * Updated `containsSemantics` and `matchSemantics` matchers to also work on `FinderBase<Semantics>`
      
      Closes #112413
      52a1a318
  2. 17 Oct, 2023 1 commit
  3. 25 Sep, 2023 1 commit
  4. 22 Sep, 2023 1 commit
  5. 20 Sep, 2023 1 commit
  6. 12 Sep, 2023 1 commit
  7. 08 Sep, 2023 1 commit
  8. 01 Sep, 2023 2 commits
  9. 23 Aug, 2023 1 commit
    • Michael Goderbauer's avatar
      Remove deprecated *TestValues from TestWindow (#131098) · ad78cf35
      Michael Goderbauer authored
      Part of https://github.com/flutter/flutter/issues/133171.
      
      Removes from `TestWindow`:
      * `localeTestValue`
      * `clearLocaleTestValue`
      * `localesTestValue`
      * `clearLocalesTestValue`
      * `initialLifecycleStateTestValue`
      * `alwaysUse24HourFormatTestValue`
      * `clearAlwaysUse24HourTestValue`
      * `brieflyShowPasswordTestValue`
      * `defaultRouteNameTestValue`
      * `clearDefaultRouteNameTestValue`
      * `semanticsEnabledTestValue`
      * `clearSemanticsEnabledTestValue`
      * `accessibilityFeaturesTestValue`
      * `clearAccessibilityFeaturesTestValue`
      
      These properties have reached the end of their deprecation period.
      ad78cf35
  10. 22 Aug, 2023 1 commit
  11. 21 Aug, 2023 1 commit
  12. 15 Aug, 2023 1 commit
    • Ian Hickson's avatar
      PaginatedDataTable improvements (#131374) · ccdf8264
      Ian Hickson authored
      - slightly improved assert message when row cell counts don't match column count.
      - more breadcrumbs in API documentation. more documentation in general.
      - added more documentation for the direction of the "ascending" arrow.
      - two samples for PaginatedDataTable.
      - make PaginatedDataTable support hot reloading across changes to the number of columns.
      - introduce matrix3MoreOrLessEquals. An earlier version of this PR used it in tests, but eventually it was not needed. The function seems useful to keep though.
      ccdf8264
  13. 14 Aug, 2023 1 commit
  14. 10 Aug, 2023 1 commit
    • pdblasi-google's avatar
      Adds SemanticsNode Finders for searching the semantics tree (#127137) · 5df1c996
      pdblasi-google authored
      * Pulled `FinderBase` out of `Finder`
        * `FinderBase` can be used for any object, not just elements
        * Terminology was updated to be more "find" related
      * Re-implemented `Finder` using `FinderBase<Element>`
        * Backwards compatibility maintained with `_LegacyFinderMixin`
      * Introduced base classes for SemanticsNode finders
      * Introduced basic SemanticsNode finders through `find.semantics`
      * Updated some relevant matchers to make use of the more generic `FinderBase`
      
      Closes #123634
      Closes #115874
      5df1c996
  15. 07 Aug, 2023 1 commit
  16. 31 Jul, 2023 1 commit
  17. 17 Jul, 2023 1 commit
    • Michael Goderbauer's avatar
      Stand-alone widget tree with multiple render trees to enable multi-view rendering (#125003) · 6f09064e
      Michael Goderbauer authored
      This change enables Flutter to generate multiple Scenes to be rendered into separate FlutterViews from a single widget tree. Each Scene is described by a separate render tree, which are all associated with the single widget tree.
      
      This PR implements the framework-side mechanisms to describe the content to be rendered into multiple views. Separate engine-side changes are necessary to provide these views to the framework and to draw the framework-generated Scene into them.
      
      ## Summary of changes
      
      The details of this change are described in [flutter.dev/go/multiple-views](https://flutter.dev/go/multiple-views). Below is a high-level summary organized by layers.
      
      ### Rendering layer changes
      
      * The `RendererBinding` no longer owns a single `renderView`. In fact, it doesn't OWN any `RenderView`s at all anymore. Instead, it offers an API (`addRenderView`/`removeRenderView`) to add and remove `RenderView`s that then will be MANAGED by the binding. The `RenderView` itself is now owned by a higher-level abstraction (e.g. the `RawView` Element of the widgets layer, see below), who is also in charge of adding it to the binding. When added, the binding will interact with the `RenderView` to produce a frame (e.g. by calling `compositeFrame` on it) and to perform hit tests for incoming pointer events. Multiple `RenderView`s can be added to the binding (typically one per `FlutterView`) to produce multiple Scenes.
      * Instead of owning a single `pipelineOwner`, the `RendererBinding` now owns the root of the `PipelineOwner` tree (exposed as `rootPipelineOwner` on the binding). Each `PipelineOwner` in that tree (except for the root) typically manages its own render tree typically rooted in one of the `RenderView`s mentioned in the previous bullet. During frame production, the binding will instruct each `PipelineOwner` of that tree to flush layout, paint, semantics etc. A higher-level abstraction (e.g. the widgets layer, see below) is in charge of adding `PipelineOwner`s to this tree.
      * Backwards compatibility: The old `renderView` and `pipelineOwner` properties of the `RendererBinding` are retained, but marked as deprecated. Care has been taken to keep their original behavior for the deprecation period, i.e. if you just call `runApp`, the render tree bootstrapped by this call is rooted in the deprecated `RendererBinding.renderView` and managed by the deprecated `RendererBinding.pipelineOwner`.
      
      ### Widgets layer changes
      
      * The `WidgetsBinding` no longer attaches the widget tree to an existing render tree. Instead, it bootstraps a stand-alone widget tree that is not backed by a render tree. For this, `RenderObjectToWidgetAdapter` has been replaced by `RootWidget`.
      * Multiple render trees can be bootstrapped and attached to the widget tree with the help of the `View` widget, which internally is backed by a `RawView` widget. Configured with a `FlutterView` to render into, the `RawView` creates a new `PipelineOwner` and a new `RenderView` for the new render tree. It adds the new `RenderView` to the `RendererBinding` and its `PipelineOwner` to the pipeline owner tree.
      * The `View` widget can only appear in certain well-defined locations in the widget tree since it bootstraps a new render tree and does not insert a `RenderObject` into an ancestor. However, almost all Elements expect that their children insert `RenderObject`s, otherwise they will not function properly. To produce a good error message when the `View` widget is used in an illegal location, the `debugMustInsertRenderObjectIntoSlot` method has been added to Element, where a child can ask whether a given slot must insert a RenderObject into its ancestor or not. In practice, the `View` widget can be used as a child of the `RootWidget`, inside the `view` slot of the `ViewAnchor` (see below) and inside a `ViewCollection` (see below). In those locations, the `View` widget may be wrapped in other non-RenderObjectWidgets (e.g. InheritedWidgets).
      * The new `ViewAnchor` can be used to create a side-view inside a parent `View`. The `child` of the `ViewAnchor` widget renders into the parent `View` as usual, but the `view` slot can take on another `View` widget, which has access to all inherited widgets above the `ViewAnchor`. Metaphorically speaking, the view is anchored to the location of the `ViewAnchor` in the widget tree.
      * The new `ViewCollection` widget allows for multiple sibling views as it takes a list of `View`s as children. It can be used in all the places that accept a `View` widget.
      
      ## Google3
      
      As of July 5, 2023 this change passed a TAP global presubmit (TGP) in google3: tap/OCL:544707016:BASE:545809771:1688597935864:e43dd651
      
      ## Note to reviewers
      
      This change is big (sorry). I suggest focusing the initial review on the changes inside of `packages/flutter` first. The majority of the changes describe above are implemented in (listed in suggested review order):
      
      * `rendering/binding.dart`
      * `widgets/binding.dart`
      * `widgets/view.dart`
      * `widgets/framework.dart`
      
      All other changes included in the PR are basically the fallout of what's implemented in those files. Also note that a lot of the lines added in this PR are documentation and tests.
      
      I am also very happy to walk reviewers through the code in person or via video call, if that is helpful.
      
      I appreciate any feedback.
      
      ## Feedback to address before submitting ("TODO")
      6f09064e
  18. 06 Jul, 2023 1 commit
  19. 13 Jun, 2023 1 commit
  20. 07 Jun, 2023 1 commit
  21. 03 Jun, 2023 1 commit
  22. 02 Jun, 2023 1 commit
    • Michael Goderbauer's avatar
      Remove LiveTestRenderView (#127882) · 4cf89cc2
      Michael Goderbauer authored
      In the multi view world, `RenderViews` are created by the `View` widget and no longer owned by the binding. Prior to this change, the `LiveTestWidgetsFlutterBinding` owned and managed a special subclass of `RenderView`, the `_LiveTestRenderView`. In the new world, where `RenderView`s can be created anywhere in the widget tree where a `View` widget is used, this setup is no longer feasible. This change removes this special `_LiveTestRenderView` and instead adds debug hocks to `RenderView` to allow the `LiveTestWidgetsFlutterBinding` to draw a debug overlay on top of the content of any `RenderView`.
      4cf89cc2
  23. 01 Jun, 2023 1 commit
  24. 26 May, 2023 1 commit
  25. 15 May, 2023 1 commit
  26. 27 Apr, 2023 1 commit
  27. 20 Apr, 2023 2 commits
  28. 12 Apr, 2023 1 commit
  29. 10 Apr, 2023 1 commit
  30. 07 Apr, 2023 2 commits
  31. 06 Apr, 2023 1 commit
  32. 31 Mar, 2023 1 commit
  33. 29 Mar, 2023 1 commit
  34. 21 Mar, 2023 2 commits
  35. 16 Mar, 2023 2 commits