Commit 9585acd4 authored by Michel Feinstein's avatar Michel Feinstein Committed by Flutter GitHub Bot

Fixing AutomaticKeepAlive Docs (#48575)

parent 9f145f6c
...@@ -733,10 +733,10 @@ abstract class BoxScrollView extends ScrollView { ...@@ -733,10 +733,10 @@ abstract class BoxScrollView extends ScrollView {
/// widget subtree with other widgets. /// widget subtree with other widgets.
/// ///
/// * Using [AutomaticKeepAlive] widgets (inserted by default when /// * Using [AutomaticKeepAlive] widgets (inserted by default when
/// [addAutomaticKeepAlives] is true). Instead of unconditionally caching the /// [addAutomaticKeepAlives] is true). [AutomaticKeepAlive] allows descendant
/// child element subtree when scrolling off-screen like [KeepAlive], /// widgets to control whether the subtree is actually kept alive or not.
/// [AutomaticKeepAlive] can let whether to cache the subtree be determined /// This behavior is in contrast with [KeepAlive], which will unconditionally keep
/// by descendant logic in the subtree. /// the subtree alive.
/// ///
/// As an example, the [EditableText] widget signals its list child element /// As an example, the [EditableText] widget signals its list child element
/// subtree to stay alive while its text field has input focus. If it doesn't /// subtree to stay alive while its text field has input focus. If it doesn't
......
...@@ -91,10 +91,10 @@ int _kDefaultSemanticIndexCallback(Widget _, int localIndex) => localIndex; ...@@ -91,10 +91,10 @@ int _kDefaultSemanticIndexCallback(Widget _, int localIndex) => localIndex;
/// `addRepaintBoundaries`. /// `addRepaintBoundaries`.
/// ///
/// * Using [AutomaticKeepAlive] widgets (inserted by default in /// * Using [AutomaticKeepAlive] widgets (inserted by default in
/// [SliverChildListDelegate] or [SliverChildListDelegate]). Instead of /// [SliverChildListDelegate] or [SliverChildListDelegate]).
/// unconditionally caching the child element subtree when scrolling /// [AutomaticKeepAlive] allows descendant widgets to control whether the
/// off-screen like [KeepAlive], [AutomaticKeepAlive] can let whether to /// subtree is actually kept alive or not. This behavior is in contrast with
/// cache the subtree be determined by descendant logic in the subtree. /// [KeepAlive], which will unconditionally keep the subtree alive.
/// ///
/// As an example, the [EditableText] widget signals its sliver child element /// As an example, the [EditableText] widget signals its sliver child element
/// subtree to stay alive while its text field has input focus. If it doesn't /// subtree to stay alive while its text field has input focus. If it doesn't
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment