I was able to reproduce this in 1.21.0-1.0.pre. According to the TextField widget's docs there is no information related to the order in which those callbacks are executed.

flutter/packages/flutter/lib/src/material/text_field.dart

Lines 133 to 258 in 1840b71

    
           /// A material design text field. 
        
           /// 
        
           /// A text field lets the user enter text, either with hardware keyboard or with 
        
           /// an onscreen keyboard. 
        
           /// 
        
           /// The text field calls the [onChanged] callback whenever the user changes the 
        
           /// text in the field. If the user indicates that they are done typing in the 
        
           /// field (e.g., by pressing a button on the soft keyboard), the text field 
        
           /// calls the [onSubmitted] callback. 
        
           /// 
        
           /// To control the text that is displayed in the text field, use the 
        
           /// [controller]. For example, to set the initial value of the text field, use 
        
           /// a [controller] that already contains some text. The [controller] can also 
        
           /// control the selection and composing region (and to observe changes to the 
        
           /// text, selection, and composing region). 
        
           /// 
        
           /// By default, a text field has a [decoration] that draws a divider below the 
        
           /// text field. You can use the [decoration] property to control the decoration, 
        
           /// for example by adding a label or an icon. If you set the [decoration] 
        
           /// property to null, the decoration will be removed entirely, including the 
        
           /// extra padding introduced by the decoration to save space for the labels. 
        
           /// 
        
           /// If [decoration] is non-null (which is the default), the text field requires 
        
           /// one of its ancestors to be a [Material] widget. 
        
           /// 
        
           /// To integrate the [TextField] into a [Form] with other [FormField] widgets, 
        
           /// consider using [TextFormField]. 
        
           /// 
        
           /// Remember to [dispose] of the [TextEditingController] when it is no longer needed. 
        
           /// This will ensure we discard any resources used by the object. 
        
           /// 
        
           /// {@tool snippet} 
        
           /// This example shows how to create a [TextField] that will obscure input. The 
        
           /// [InputDecoration] surrounds the field in a border using [OutlineInputBorder] 
        
           /// and adds a label. 
        
           /// 
        
           /// ![](https://flutter.github.io/assets-for-api-docs/assets/material/text_field.png) 
        
           /// 
        
           /// ```dart 
        
           /// TextField( 
        
           ///   obscureText: true, 
        
           ///   decoration: InputDecoration( 
        
           ///     border: OutlineInputBorder(), 
        
           ///     labelText: 'Password', 
        
           ///   ), 
        
           /// ) 
        
           /// ``` 
        
           /// {@end-tool} 
        
           /// 
        
           /// ## Reading values 
        
           /// 
        
           /// A common way to read a value from a TextField is to use the [onSubmitted] 
        
           /// callback. This callback is applied to the text field's current value when 
        
           /// the user finishes editing. 
        
           /// 
        
           /// {@tool dartpad --template=stateful_widget_material} 
        
           /// 
        
           /// This sample shows how to get a value from a TextField via the [onSubmitted] 
        
           /// callback. 
        
           /// 
        
           /// ```dart 
        
           /// TextEditingController _controller; 
        
           /// 
        
           /// void initState() { 
        
           ///   super.initState(); 
        
           ///   _controller = TextEditingController(); 
        
           /// } 
        
           /// 
        
           /// void dispose() { 
        
           ///   _controller.dispose(); 
        
           ///   super.dispose(); 
        
           /// } 
        
           /// 
        
           /// Widget build(BuildContext context) { 
        
           ///   return Scaffold( 
        
           ///     body: Center( 
        
           ///       child: TextField( 
        
           ///         controller: _controller, 
        
           ///         onSubmitted: (String value) async { 
        
           ///           await showDialog<void>( 
        
           ///             context: context, 
        
           ///             builder: (BuildContext context) { 
        
           ///               return AlertDialog( 
        
           ///                 title: const Text('Thanks!'), 
        
           ///                 content: Text ('You typed "$value".'), 
        
           ///                 actions: <Widget>[ 
        
           ///                   FlatButton( 
        
           ///                     onPressed: () { Navigator.pop(context); }, 
        
           ///                     child: const Text('OK'), 
        
           ///                   ), 
        
           ///                 ], 
        
           ///               ); 
        
           ///             }, 
        
           ///           ); 
        
           ///         }, 
        
           ///       ), 
        
           ///     ), 
        
           ///   ); 
        
           /// } 
        
           /// ``` 
        
           /// {@end-tool} 
        
           /// 
        
           /// For most applications the [onSubmitted] callback will be sufficient for 
        
           /// reacting to user input. 
        
           /// 
        
           /// The [onEditingComplete] callback also runs when the user finishes editing. 
        
           /// It's different from [onSubmitted] because it has a default value which 
        
           /// updates the text controller and yields the keyboard focus. Applications that 
        
           /// require different behavior can override the default [onEditingComplete] 
        
           /// callback. 
        
           /// 
        
           /// Keep in mind you can also always read the current string from a TextField's 
        
           /// [TextEditingController] using [TextEditingController.text]. 
        
           /// 
        
           /// See also: 
        
           /// 
        
           ///  * <https://material.io/design/components/text-fields.html> 
        
           ///  * [TextFormField], which integrates with the [Form] widget. 
        
           ///  * [InputDecorator], which shows the labels and other visual elements that 
        
           ///    surround the actual text editing widget. 
        
           ///  * [EditableText], which is the raw text editing control at the heart of a 
        
           ///    [TextField]. The [EditableText] widget is rarely used directly unless 
        
           ///    you are implementing an entirely different design language, such as 
        
           ///    Cupertino. 
        
           ///  * Learn how to use a [TextEditingController] in one of our 
        
           ///    [cookbook recipe](https://flutter.dev/docs/cookbook/forms/text-field-changes#2-use-a-texteditingcontroller)s.

flutter doctor -v

[✓] Flutter (Channel dev, 1.21.0-1.0.pre, on Mac OS X 10.15.5 19F101, locale en-AO)
    • Flutter version 1.21.0-1.0.pre at /Users/pedro/dev/SDKs/flutter_dev
    • Framework revision f25bd9c55c (2 days ago), 2020-07-14 20:26:01 -0400
    • Engine revision 99c2b3a245
    • Dart version 2.9.0 (build 2.9.0-21.0.dev 20bf2fcf56)

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.0)
    • Android SDK at /Users/pedro/Library/Android/sdk
    • Platform android-30, build-tools 30.0.0
    • Java binary at: /Users/pedro/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/193.6514223/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.5)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.5, Build version 11E608c
    • CocoaPods version 1.9.3

[✓] Chrome - develop for the web
    • CHROME_EXECUTABLE = /Applications/Google Chrome.app/Contents/MacOS/google-chrome-unsafe

[✓] Android Studio (version 4.0)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 47.1.2
    • Dart plugin version 193.7361
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)

[✓] Android Studio (version 4.0)
    • Android Studio at /Users/pedro/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/193.6514223/Android Studio.app/Contents
    • Flutter plugin version 47.1.2
    • Dart plugin version 193.7361
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)

[✓] VS Code (version 1.47.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.12.1

[✓] Connected device (4 available)
    • AOSP on IA Emulator (mobile) • emulator-5554 • android-x86    • Android 9 (API 28) (emulator)
    • macOS (desktop)              • macos         • darwin-x64     • Mac OS X 10.15.5 19F101
    • Web Server (web)             • web-server    • web-javascript • Flutter Tools
    • Chrome (web)                 • chrome        • web-javascript • Google Chrome 83.0.4103.116

• No issues found!
Process finished with exit code 0

	/// A material design text field.
	///
	/// A text field lets the user enter text, either with hardware keyboard or with
	/// an onscreen keyboard.
	///
	/// The text field calls the [onChanged] callback whenever the user changes the
	/// text in the field. If the user indicates that they are done typing in the
	/// field (e.g., by pressing a button on the soft keyboard), the text field
	/// calls the [onSubmitted] callback.
	///
	/// To control the text that is displayed in the text field, use the
	/// [controller]. For example, to set the initial value of the text field, use
	/// a [controller] that already contains some text. The [controller] can also
	/// control the selection and composing region (and to observe changes to the
	/// text, selection, and composing region).
	///
	/// By default, a text field has a [decoration] that draws a divider below the
	/// text field. You can use the [decoration] property to control the decoration,
	/// for example by adding a label or an icon. If you set the [decoration]
	/// property to null, the decoration will be removed entirely, including the
	/// extra padding introduced by the decoration to save space for the labels.
	///
	/// If [decoration] is non-null (which is the default), the text field requires
	/// one of its ancestors to be a [Material] widget.
	///
	/// To integrate the [TextField] into a [Form] with other [FormField] widgets,
	/// consider using [TextFormField].
	///
	/// Remember to [dispose] of the [TextEditingController] when it is no longer needed.
	/// This will ensure we discard any resources used by the object.
	///
	/// {@tool snippet}
	/// This example shows how to create a [TextField] that will obscure input. The
	/// [InputDecoration] surrounds the field in a border using [OutlineInputBorder]
	/// and adds a label.
	///
	/// ![](https://flutter.github.io/assets-for-api-docs/assets/material/text_field.png)
	///
	/// ```dart
	/// TextField(
	/// obscureText: true,
	/// decoration: InputDecoration(
	/// border: OutlineInputBorder(),
	/// labelText: 'Password',
	/// ),
	/// )
	/// ```
	/// {@end-tool}
	///
	/// ## Reading values
	///
	/// A common way to read a value from a TextField is to use the [onSubmitted]
	/// callback. This callback is applied to the text field's current value when
	/// the user finishes editing.
	///
	/// {@tool dartpad --template=stateful_widget_material}
	///
	/// This sample shows how to get a value from a TextField via the [onSubmitted]
	/// callback.
	///
	/// ```dart
	/// TextEditingController _controller;
	///
	/// void initState() {
	/// super.initState();
	/// _controller = TextEditingController();
	/// }
	///
	/// void dispose() {
	/// _controller.dispose();
	/// super.dispose();
	/// }
	///
	/// Widget build(BuildContext context) {
	/// return Scaffold(
	/// body: Center(
	/// child: TextField(
	/// controller: _controller,
	/// onSubmitted: (String value) async {
	/// await showDialog<void>(
	/// context: context,
	/// builder: (BuildContext context) {
	/// return AlertDialog(
	/// title: const Text('Thanks!'),
	/// content: Text ('You typed "$value".'),
	/// actions: <Widget>[
	/// FlatButton(
	/// onPressed: () { Navigator.pop(context); },
	/// child: const Text('OK'),
	/// ),
	/// ],
	/// );
	/// },
	/// );
	/// },
	/// ),
	/// ),
	/// );
	/// }
	/// ```
	/// {@end-tool}
	///
	/// For most applications the [onSubmitted] callback will be sufficient for
	/// reacting to user input.
	///
	/// The [onEditingComplete] callback also runs when the user finishes editing.
	/// It's different from [onSubmitted] because it has a default value which
	/// updates the text controller and yields the keyboard focus. Applications that
	/// require different behavior can override the default [onEditingComplete]
	/// callback.
	///
	/// Keep in mind you can also always read the current string from a TextField's
	/// [TextEditingController] using [TextEditingController.text].
	///
	/// See also:
	///
	/// * <https://material.io/design/components/text-fields.html>
	/// * [TextFormField], which integrates with the [Form] widget.
	/// * [InputDecorator], which shows the labels and other visual elements that
	/// surround the actual text editing widget.
	/// * [EditableText], which is the raw text editing control at the heart of a
	/// [TextField]. The [EditableText] widget is rarely used directly unless
	/// you are implementing an entirely different design language, such as
	/// Cupertino.
	/// * Learn how to use a [TextEditingController] in one of our
	/// [cookbook recipe](https://flutter.dev/docs/cookbook/forms/text-field-changes#2-use-a-texteditingcontroller)s.

Uh oh!

TextField documentation should say the order in which onSubmitted vs onEditingComplete vs onChanged happens #27581

Description

Metadata

Metadata

Assignees

Labels

Type

Fields

Projects

Milestone

Relationships

Development

Issue actions