feat: restore Emulator app history routing - #10
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary\n- Restore push, replace, and popstate routing for launcher home, systems, and linked games.\n- Preserve host parameters and non-route fragments.\n- Keep a running player alive while traversing launcher pages.\n- Reuse the exact running ROM, file, and core without fetch, reset, hot-swap, or iframe reload.\n- Prevent stale async route loads from launching after newer navigation.\n- Ship Emulator 1.4.1 and add focused routing tests to CI.\n\n## Validation\n- npm run check passed.\n- npm test: 7 routing tests passed.\n- npm run build passed.\n- npm run qdn:package passed.\n- Manifest and ZIP integrity checks passed.\n- Chromium render/version smoke passed.\n- git diff --check passed.