build method

@override Widget build(BuildContext context)

Describes the part of the user interface represented by this widget.

The framework calls this method when this widget is inserted into the tree in a given BuildContext and when the dependencies of this widget change (e.g., an InheritedWidget referenced by this widget changes). This method can potentially be called in every frame and should not have any side effects beyond building a widget.

The framework replaces the subtree below this widget with the widget returned by this method, either by updating the existing subtree or by removing the subtree and inflating a new subtree, depending on whether the widget returned by this method can update the root of the existing subtree, as determined by calling Widget.canUpdate.

Typically implementations return a newly created constellation of widgets that are configured with information from this widget's constructor and from the given BuildContext.

The given BuildContext contains information about the location in the tree at which this widget is being built. For example, the context provides the set of inherited widgets for this location in the tree. A given widget might be built with multiple different BuildContext arguments over time if the widget is moved around the tree or if the widget is inserted into the tree in multiple places at once.

The implementation of this method must only depend on:

• the fields of the widget, which themselves must not change over time, and
• any ambient state obtained from the context using BuildContext.dependOnInheritedWidgetOfExactType.

If a widget's build method is to depend on anything else, use a StatefulWidget instead.

See also:

• StatelessWidget, which contains the discussion on performance considerations.

Implementation

@override
Widget build(BuildContext context) {
  var media = MediaQuery.of(context);
  // **The wrappers are unconditional, and that is not tidiness.** A widget
  // that returns its child bare at zero and wraps it at 336 *reparents the
  // app* the moment the keyboard moves: every `State` under it is disposed
  // and rebuilt, which loses the focus, closes the text input connection and
  // empties whatever had been typed. Measured — a scenario tapping a field
  // saw `TextInput.show` immediately followed by `clearClient`, and the
  // keyboard it had just asked for went straight back down.
  //
  // So the shape stays put and only the numbers move. Down costs one
  // `MediaQuery` with the data it was given and a zero-height band.
  return MediaQuery(
    // The arithmetic, and all three numbers of it. Getting only the first is
    // how a fake keyboard ends up with a `SafeArea` floating 34 points above
    // it: `MediaQueryData.fromView` reads `view.padding` directly rather
    // than deriving it from the insets, so a driver that raises the insets
    // and leaves the padding alone is describing a phone that does not
    // exist. A real embedder eats the home indicator — measured on eight
    // simulators and an emulator, `padding.bottom` is 0 on every one of them
    // while the keyboard is up — and `viewPadding` is what still remembers
    // the device underneath.
    data: height <= 0
        ? media
        : media.copyWith(
            padding: media.padding.copyWith(
              bottom: math.max(0, media.padding.bottom - height),
            ),
            viewInsets: media.viewInsets.copyWith(bottom: height),
          ),
    child: FakeKeyboardSlab(
      height: height,
      platform: platform,
      variant: variant,
      child: child,
    ),
  );
}