Fix bug #1309: me.navigate() now works consistently during page load #1321
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previously, when me.navigate() was called during initial page load
(e.g., in an on_load handler), the URL would change in the browser
but the target page would not actually render. This was because the
navigate command was sent to the client, but the server immediately
ended the response stream without actually loading the target page.
This fix adds logic to check for navigate commands after the initial
page load and on_load handler execution. If a navigate command is
present, it is processed the same way as during event handling:
the target page, including running its on_load handler if present
This enables common authentication redirect patterns where
unauthenticated users are automatically redirected to a login page.
Also includes a test file demonstrating the fix.