Every change Boring Doc has indexed from official sources: breaking-change guides, hotfix changelogs and release notes. Filter by category, impact, platform, series and evidence type.
174 changes · page 4 of 5
`ScrollBehavior`s now allow or disallow drag scrolling from specified `PointerDeviceKind`s. `ScrollBehavior.dragDevices`, by default, allows scrolling widgets to be dragged by all `PointerDeviceKind`s except for `PointerDeviceKind.mouse`.
The `WidgetTester.enterText` and `TestTextInput.enterText` methods now move the caret to the end of the input text.
`OneSequenceGestureRecognizer.addAllowedPointer()` was changed to take a `PointerDownEvent`, like its superclass. Previously, it accepted the more general `PointerEvent` type, which was incorrect.
The `package:flutter_lints` defines the latest set of recommended lints that encourage good coding practices for Flutter apps, packages, and plugins. Projects created with `flutter create` using Flutter version 2.5 or newer are already enabled to use the latest set of recommended lints. Projects created prior to that version can upgrade to it with the instructions in this guide.
The `AnimationSheetBuilder.display` and `sheetSize` methods are deprecated, and should be replaced with `AnimationSheetBuilder.collate`.
The following methods have been replaced by APIs in the `flutter_test` package:
Flutter now renders all web platform views in a consistent location of the DOM, as direct children of `flt-glass-pane` (regardless of the rendering backend: `html` or `canvaskit`). Platform views are then _"slotted"_ into the correct position of the App's DOM with standard HTML features.
How to update a Windows project to use the idiomatic run loop
In accordance with Flutter's Deprecation Policy, deprecated APIs that reached end of life after the 2.2 stable release have been removed.
The ThemeData accentColor, accentColorBrightness, accentIconTheme and accentTextTheme properties have been deprecated.
`ScrollBehavior`s now automatically apply `Scrollbar`s to scrolling widgets on desktop platforms - Mac, Windows and Linux.
A `BuildContext` parameter was added to `TextEditingController.buildTextSpan`.
`FlutterActivity` or `FlutterFragment`, and don't manually embed a `FlutterView` inside your own custom `Activity` (this should be uncommon), you can stop reading.
Flutter now defaults to _not_ clip except for a few specialized widgets (such as `ClipRect`). To override the no-clip default, explicitly set `clipBehavior` in widgets constructions.
A new method named `computeDryLayout` was added to the `RenderBox` protocol. Subclasses of `RenderBox` are expected to implement it to correctly report their desired size given a set of `BoxConstraints` during intrinsic calculations. Subclasses that implement `computeDryLayout` no longer need to override `performResize`.
This migration guide describes conversion of code that uses the `nullOk` parameter on multiple `of` static accessors and related accessors to use alternate APIs with nullable return values.
Flutter now applies the semantic label of `button` to all interactive Material Chips for accessibility purposes.
The `SnackBar` API within the `Scaffold` is now handled by the `ScaffoldMessenger`, one of which is available by default within the context of a `MaterialApp`.
The `ThemeData` properties that controlled the look of selected text in Material widgets have been moved into their own `TextSelectionTheme`. These properties include `cursorColor`, `textSelectionColor`, and `textSelectionHandleColor`. The defaults for these properties have also been changed to match the Material Design specification.
To control the behavior of `maxLength` in the `LengthLimitingTextInputFormatter`, use `maxLengthEnforcement` instead of the now-deprecated `maxLengthEnforced`.
If you write Java JUnit tests (such as Robolectric tests) against the Flutter engine's Java embedding and used the `FlutterMain.setIsRunningInRobolectricTest(true)` API, replace it with the following:
In accordance with Flutter's Deprecation Policy, deprecated APIs that reached end of life after the 1.22 stable release have been removed. This is the first time that deprecated APIs have been removed from Flutter, and some of these deprecations predate our migration guide policy.
The existing cupertino_icons, 0.1.3 icons, are based on iOS 11 aesthetics with sharp angles and thin lines.
The previous auto validation API for the `Form` and `FormField` widgets didn't control when auto validation should occur. So the auto validation for these widgets always happened on first build when the widget was first visible to the user, and you weren't able to control when the auto validation should happen.
The `flutter create` templates for apps and plugins no longer create Android wrapping based on the v1 Android embedding as part of our gradual Android v1 embedding deprecation process described in our Android Migration Summary.
In Flutter an `Intent` is an object that's typically bound to a keyboard key combination using the `Shortcuts` widget. An `Intent` can be bound to an `Action`, which can update the application's state or perform other operations. In the course of using this API, we identified several drawbacks in the design, so we have updated the Actions API to make it easier to use and understand.
A new getter, `TextInputClient.currentAutofillScope`, was added to the `TextInputClient` interface; all `TextInputClient` subclasses must provide a concrete implementation of `currentAutofillScope`.
A new set of basic material button widgets and themes have been added to Flutter. The original classes have been deprecated and will eventually be removed. The overall goal is to make buttons more flexible, and easier to configure via constructor parameters or themes.
Instances of `Dialog`, as well as `SimpleDialog`, `AlertDialog`, and `showTimePicker`, now have a default shape of a `RoundedRectangleBorder` with a `BorderRadius` of 4.0 pixels. This matches the current specifications of Material Design. Prior to this change, the default behavior for `Dialog.shape`'s `BorderRadius` was 2.0 pixels.
The framework throws an assertion error when it detects there are multiple navigators registered with one hero controller scope.
A new boolean getter `isWaitingForExitingDecision` was added to the route transition record and the `isEntering` getter was renamed to `isWaitingForEnteringDecision`. In the `resolve()` method for the transition delegate, use the `isWaitingForExitingDecision` to check if an exiting route actually needs an explicit decision on how to transition off the screen. If you try to make a decision for an existing route that _isn't_ waiting for a decision, Flutter throws an assertion error.
Instances of `RenderEditable` must be laid out before processing hit testing. Trying to hit-test a `RenderEditable` object before layout results in an assertion such as the following:
The services layer now depends on the scheduler layer. Previously, the opposite was true. This may affect you if you have defined custom bindings overriding Flutter's `SchedulerBinding` or `ServicesBinding`.
We changed the semantics traverse order of the overlay entries in modal routes. Accessibility talk back or voice over now focuses the scope of a modal route first instead of its modal barrier.
A new method,`void showAutocorrectionPromptRect(int start, int end)`, was added to the `TextInputClient` interface.
The `TestWidgetsFlutterBinding.clock` now comes from `package:clock` and not `package:quiver`.
Instances of `TextField` must have a `MaterialLocalizations` present in the widget tree. Trying to instantiate a `TextField` without the proper localizations results in an assertion such as the following:
Removed Flutter's `FloatingActionButton` (FAB) dependency on `ThemeData` accent properties.
Two new values were added to the `TargetPlatform` enum that could require additional cases in switch statements that switch on a `TargetPlatform` and don't include a `default:` case.
The local position returned by `AnnotatedRegionLayers` in an annotation search has been changed to be relative to the clipping region instead of the layer. This makes the local position more meaningful and reliable, but breaks code that directly performs annotation searches and uses the local position.