Repository navigation
Fix literal hashes in tile paths (6.10.1) - #20
Merged
Merged
Conversation
🚀 Deploying Preview to Cloudflare 🚀Preview Deployments by commit
|
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
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.
Tile filenames containing a raw # were truncated by browser fragment parsing, causing navigation to 404. Repair incomplete JavStore item paths only when the fragment contains the missing -pn.html ending, preserving existing escapes and trailing query strings or legitimate fragments. Apply the repair during tile processing, including added and changed tiles and context-menu navigation.
Add four regression tests covering repairs, unchanged links, dynamic tiles, history recording, and existing visits to correctly escaped URLs. Truncated legacy history is not migrated because its missing path cannot be recovered reliably.
Bump @Version, SCRIPT_VERSION, and WORKER_VERSION to 6.10.1 and add the matching changelog section. The existing main-branch release workflow publishes the asset served by the stable @updateURL and @downloadurl.
Validation: userscript syntax check, diff whitespace check, and all 81 tests passed locally.