Building off of wanderview@'s WIP PR that defines navigation start, and doing the same for navigation end.
I think that these are all the steps needed to account for server redirects. Our code adds logic around redirect chaining, committed/uncommitted redirects, and stateful/stateless bounces. But AFAICT these are only for metrics or experimental features.
In a future PR I'll include client-side redirect detection. These should be able to reuse the same hooks for navigation start/end.
Building off of wanderview@'s WIP PR that defines navigation start, and doing the same for navigation end.
I think that these are all the steps needed to account for server redirects. Our code adds logic around redirect chaining, committed/uncommitted redirects, and stateful/stateless bounces. But AFAICT these are only for metrics or experimental features.
In a future PR I'll include client-side redirect detection. These should be able to reuse the same hooks for navigation start/end.
Preview | Diff