firka/flutter
firka/flutter
4
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Fixing AutomaticKeepAlive Docs (#48575)

Browse Source
This commit is contained in:
Michel Feinstein 2020-01-13 22:18:02 -03:00 committed by Flutter GitHub Bot
parent 9f145f6ced
commit 9585acd478
2 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
packages/flutter/lib/src/widgets/scroll_view.dart
View File

@ -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

8
packages/flutter/lib/src/widgets/sliver.dart
View File

@ -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