From ba7cbea406f8d86a3e1e888d53202bf4e9050903 Mon Sep 17 00:00:00 2001 From: Ian Hickson Date: Wed, 5 Oct 2022 00:39:09 -0700 Subject: [PATCH] Fix outdated comment about overflow (#112595) --- packages/flutter/lib/src/cupertino/refresh.dart | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/packages/flutter/lib/src/cupertino/refresh.dart b/packages/flutter/lib/src/cupertino/refresh.dart index 351044a855..d98e516dcb 100644 --- a/packages/flutter/lib/src/cupertino/refresh.dart +++ b/packages/flutter/lib/src/cupertino/refresh.dart @@ -380,13 +380,13 @@ class CupertinoSliverRefreshControl extends StatefulWidget { ) { final double percentageComplete = clampDouble(pulledExtent / refreshTriggerPullDistance, 0.0, 1.0); - // Place the indicator at the top of the sliver that opens up. Note that we're using - // a Stack/Positioned widget because the CupertinoActivityIndicator does some internal - // translations based on the current size (which grows as the user drags) that makes - // Padding calculations difficult. Rather than be reliant on the internal implementation - // of the activity indicator, the Positioned widget allows us to be explicit where the - // widget gets placed. Also note that the indicator should appear over the top of the - // dragged widget, hence the use of Overflow.visible. + // Place the indicator at the top of the sliver that opens up. We're using a + // Stack/Positioned widget because the CupertinoActivityIndicator does some + // internal translations based on the current size (which grows as the user drags) + // that makes Padding calculations difficult. Rather than be reliant on the + // internal implementation of the activity indicator, the Positioned widget allows + // us to be explicit where the widget gets placed. The indicator should appear + // over the top of the dragged widget, hence the use of Clip.none. return Center( child: Stack( clipBehavior: Clip.none,