- 09 Jan, 2024 1 commit
-
-
SharbelOkzan authored
Introduced `validateGranually` which, apart from announcing the errors to the UI, returns a `Map<Key, bool>` providing more granular validation details: The results of calling `validate` on each `FormField` and their corresponding widget keys. * related issue: #135363
-
- 15 Dec, 2023 1 commit
-
-
Polina Cherkasova authored
-
- 01 Nov, 2023 1 commit
-
-
Binni Goel authored
## Description This PR fixes typos in - `editable_text_show_on_screen_test.dart` - `form_test.dart` - `framework.dart`
-
- 25 Sep, 2023 1 commit
-
-
Edgar Jan authored
In the FormField widget, if a validator is initially set (and validation fails), then subsequently the validator is set to null, the form incorrectly retains its error state. This is not expected behavior as removing the validator should clear any validation errors.
-
- 14 Sep, 2023 1 commit
-
-
Kostia Sokolovskyi authored
-
- 10 Aug, 2023 1 commit
-
-
Fré Dumazy authored
Adds a getter to access the value of the private `RestorableBool _hasInteractedByUser`. *List which issues are fixed by this PR. You must list at least one issue.* Fixes #131538
-
- 29 Mar, 2023 1 commit
-
-
hangyu authored
Use SemanticsService.announce to announce form text validation error
-
- 14 Oct, 2021 1 commit
-
-
Kate Lovett authored
-
- 08 Oct, 2021 3 commits
-
-
Ian Hickson authored
-
Zachary Anderson authored
This reverts commit 5fd259be.
-
Ian Hickson authored
-
- 07 Oct, 2021 1 commit
-
-
Kate Lovett authored
-
- 06 Oct, 2021 1 commit
-
-
Kate Lovett authored
-
- 01 Jun, 2021 1 commit
-
-
Alexandre Ardhuin authored
-
- 28 Apr, 2021 1 commit
-
-
Alexandre Ardhuin authored
-
- 21 Apr, 2021 1 commit
-
-
Phil Quitslund authored
-
- 09 Dec, 2020 1 commit
-
-
Alex Li authored
-
- 12 Oct, 2020 1 commit
-
-
Darren Austin authored
-
- 28 Sep, 2020 1 commit
-
-
Pedro Massango authored
* Add back autovalidate property * Add autovalidate property back (include tests) * Fix typos * One more test :)
-
- 24 Aug, 2020 1 commit
-
-
Alex Li authored
-
- 16 Jul, 2020 1 commit
-
-
Pedro Massango authored
-
- 11 Jun, 2020 1 commit
-
-
Alexandre Ardhuin authored
* add language version 2.8 in packages/flutter * enable non-nullable analyzer flag
-
- 19 Feb, 2020 1 commit
-
-
Tjong Anthony authored
-
- 27 Nov, 2019 1 commit
-
-
Ian Hickson authored
* Update project.pbxproj files to say Flutter rather than Chromium Also, the templates now have an empty organization so that we don't cause people to give their apps a Flutter copyright. * Update the copyright notice checker to require a standard notice on all files * Update copyrights on Dart files. (This was a mechanical commit.) * Fix weird license headers on Dart files that deviate from our conventions; relicense Shrine. Some were already marked "The Flutter Authors", not clear why. Their dates have been normalized. Some were missing the blank line after the license. Some were randomly different in trivial ways for no apparent reason (e.g. missing the trailing period). * Clean up the copyrights in non-Dart files. (Manual edits.) Also, make sure templates don't have copyrights. * Fix some more ORGANIZATIONNAMEs
-
- 10 Jul, 2019 1 commit
-
-
Justin McCandless authored
Show and hide the text selection menu at the correct time with various gestures in the text field.
-
- 10 Apr, 2019 1 commit
-
-
Todd Volkert authored
This reverts commit 949023b2.
-
- 08 Apr, 2019 1 commit
-
-
Todd Volkert authored
When submitting data to a server, callers need a callback that will get invoked after all the individual form fields are saved. If they have a button that submits the form, they could just do this logic in the click handler for the button (save the form, then submit to the server), but if they have more ways than one to submit the form (i.e. hitting enter while in a text form field), then it becomes more convoluted and calls for a unified callback that will get notified when the form is submitted.
-
- 01 Mar, 2019 1 commit
-
-
Alexandre Ardhuin authored
* add trailing commas on list/map/parameters * add trailing commas on Invocation with nb of arg>1 * add commas for widget containing widgets * add trailing commas if instantiation contains trailing comma * revert bad change
-
- 29 Jan, 2019 1 commit
-
-
jslavitz authored
* Fixes cursor on iOS devices
-
- 16 Oct, 2018 1 commit
-
-
Alexandre Ardhuin authored
* Future<void> main * Future<void>.delayed * prefer_void_to_Null * address review comments
-
- 12 Sep, 2018 1 commit
-
-
Alexandre Ardhuin authored
* enable lint unnecessary_new * fix tests * fix tests * fix tests
-
- 26 Jun, 2018 1 commit
-
-
Ian Hickson authored
-
- 14 Mar, 2018 1 commit
-
-
Hans Muller authored
-
- 16 Feb, 2018 1 commit
-
-
Alexandre Ardhuin authored
* fix potential call on null * review
-
- 01 Feb, 2018 1 commit
-
-
Alexandre Ardhuin authored
-
- 29 Sep, 2017 1 commit
-
-
Chris Bracken authored
This patch fixes a collection of issues with widgets involved in text editing: * Fire widget.onChanged on EditableText value change: The value of an EditableText is composed of the text value as well as other editing-related data such as selection-related information. Previously, widget.onChanged() was only called for updates via updateEditingValue(). For pastes via a TextSelectionOverlay, updates are signalled via _handleSelectionOverlayChanged(), which only ever triggered widget.onSelectionChanged(), but not widget.onChanged(). Both updateEditingValue() and _handleSelectionOverlayChanged() perform the value update via _formatAndSetValue(), which is where this patch moves the widget.onChanged() call. * Correctly update TextFormField value on edits via controller: The textual value of a TextFormField exists in two locations: 1. FormField.value, as with all FormFields and subclasses. 2. TextEditingController.value associated with the TextField underlying the TextFormField. Previously, edits to the TextEditingController associated with a TextFormField resulted in updates to the rendered TextField widget, but did not update TextFormField.value. FormField.value is updated via FormField's onChanged function, which is called from the EditableText underlying the TextField underlying the TextFormField. EditableText only fires onChanged when it receives changes from the engine. It does not fire onChanged for changes made to the underlying TextController, since the owner of the TextController is the one making these changes and thus, already aware of them. FormField, however, *does* need to listen to these changes to update its value. * Adds an initialValue parameter to the TextFormField constructor: FormField's constructor already takes an initialValue parameter, which specifies the initial value in the field, which is also the value to which reset() returns the field. Previously, TextFormField took its initial value from the controller value (if a controller was passed in) or the empty string (if not). This had the undesirable effect that calling reset() always resets the value to the current value of the controller... i.e., does nothing. We now take an initial value explicitly.
-
- 07 Sep, 2017 1 commit
-
-
Ian Hickson authored
-
- 05 Sep, 2017 1 commit
-
-
Adam Barth authored
Fixes #11855
-
- 14 Apr, 2017 1 commit
-
-
Hans Muller authored
-
- 11 Apr, 2017 1 commit
-
-
xster authored
Rename State.config to State.widget Rename State.didUpdateConfig to State.didUpdateWidget Renamed all State subclasses' local variables named config to something else
-