From 9585acd4787b5aaa5d775e1d9734ffff1697fbc9 Mon Sep 17 00:00:00 2001 From: Michel Feinstein Date: Mon, 13 Jan 2020 22:18:02 -0300 Subject: [PATCH] Fixing AutomaticKeepAlive Docs (#48575) --- packages/flutter/lib/src/widgets/scroll_view.dart | 8 ++++---- packages/flutter/lib/src/widgets/sliver.dart | 8 ++++---- 2 files changed, 8 insertions(+), 8 deletions(-) diff --git a/packages/flutter/lib/src/widgets/scroll_view.dart b/packages/flutter/lib/src/widgets/scroll_view.dart index 402d820fd2..73107c04dc 100644 --- a/packages/flutter/lib/src/widgets/scroll_view.dart +++ b/packages/flutter/lib/src/widgets/scroll_view.dart @@ -733,10 +733,10 @@ abstract class BoxScrollView extends ScrollView { /// widget subtree with other widgets. /// /// * Using [AutomaticKeepAlive] widgets (inserted by default when -/// [addAutomaticKeepAlives] is true). Instead of unconditionally caching the -/// child element subtree when scrolling off-screen like [KeepAlive], -/// [AutomaticKeepAlive] can let whether to cache the subtree be determined -/// by descendant logic in the subtree. +/// [addAutomaticKeepAlives] is true). [AutomaticKeepAlive] allows descendant +/// widgets to control whether the subtree is actually kept alive or not. +/// This behavior is in contrast with [KeepAlive], which will unconditionally keep +/// the subtree alive. /// /// 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 diff --git a/packages/flutter/lib/src/widgets/sliver.dart b/packages/flutter/lib/src/widgets/sliver.dart index 4f6598ff36..2f9a8e4aa6 100644 --- a/packages/flutter/lib/src/widgets/sliver.dart +++ b/packages/flutter/lib/src/widgets/sliver.dart @@ -91,10 +91,10 @@ int _kDefaultSemanticIndexCallback(Widget _, int localIndex) => localIndex; /// `addRepaintBoundaries`. /// /// * Using [AutomaticKeepAlive] widgets (inserted by default in -/// [SliverChildListDelegate] or [SliverChildListDelegate]). Instead of -/// unconditionally caching the child element subtree when scrolling -/// off-screen like [KeepAlive], [AutomaticKeepAlive] can let whether to -/// cache the subtree be determined by descendant logic in the subtree. +/// [SliverChildListDelegate] or [SliverChildListDelegate]). +/// [AutomaticKeepAlive] allows descendant widgets to control whether the +/// subtree is actually kept alive or not. This behavior is in contrast with +/// [KeepAlive], which will unconditionally keep the subtree alive. /// /// 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