The patch CL to submit alongside this PR: https://critique.corp.google.com/cl/793706017

This PR was merged into the repository by commit 4e0fc81.

The changes were merged into the following branches: main

@JeanMeche I noticed a change in the behavior of lastSuccessfulNavigation.

On a direct page visit (the initial navigation), the lastSuccessfulNavigation() signal is populated with a Navigation object (id: 1). In the previous versions Angular (for example, 20.2), lastSuccessfulNavigation would have been null initially.

Is this new behavior intentional and an expected part of the new signal-based API? I couldn't find info of this specific behavior in the PR, so I wanted to confirm.

Thank you for the clarification.

@IgorSedov Do you have a reproduction? There were no changes to the timing of the updates in this CL

@atscott My bad. Thanks for the quick response. I found the problem on my end.

I tested in different configurations (SSR, Zoneless, v20/v21) and everything is fine.

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}