Skip to content

Conversation

@justinmc
Copy link
Contributor

@justinmc justinmc commented Aug 4, 2025

This PR spawned out of flutter/flutter#165832 (comment). That PR will change the default page transition and turn on predictive back by default. While there is no API breakage, users may encounter test breakages in tests that indirectly depend on the default page transition and/or its duration. Several of these kinds of breakages were encountered in flutter/flutter#165832 in the framework tests, customer tests, and Google tests.

This PR should explain:

  • What predictive back is.
  • How to make sure an app supports predictive back.
  • What the new Fade Fowards page transition looks like.
  • How to manually change the page transition back to the old one.
  • How to write tests that don't depend on the page transition and its duration.

Issues fixed by this PR (if any): n/a

PRs or commits this PR depends on (if any): flutter/flutter#165832

Presubmit checklist

  • If you are unwilling, or unable, to sign the CLA, even for a tiny, one-word PR, please file an issue instead of a PR.
  • If this PR is not meant to land until a future stable release, mark it as draft with an explanation.
  • This PR follows the Google Developer Documentation Style Guidelines—for example, it doesn't use i.e. or e.g., and it avoids I and we (first-person pronouns).
  • This PR uses semantic line breaks
    of 80 characters or fewer.

@justinmc justinmc self-assigned this Aug 4, 2025
@justinmc justinmc changed the title Predictive back transition Predictive back transition breaking change announcement Aug 4, 2025
@sfshaza2
Copy link
Contributor

Just a reminder that we don't need to wait for a release to land this, @justinmc. Feel free to finish this PR and submit!

@sfshaza2 sfshaza2 added the review.await-update Awaiting Updates after Edits label Sep 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

review.await-update Awaiting Updates after Edits

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants