fix: properly handle protocol URLs and file associations on Windows #3076
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.
Fix protocol registration to specify electron path and app path in development mode
Add URL detection in second-instance handler to capture Windows command-line arguments
Extract protocol URLs (opds://, thorium://, http://, https://) from argv array
Improve OPDS feed title extraction using hostname or path segments
Remove unnecessary initialization delay in OPDS URL processing
This fixes two related issues on Windows:
Both issues were caused by Windows command-line arguments not being properly
passed to the second instance handler. The fix ensures argv is correctly
processed for both protocol URLs and file paths.
Fixes the issue where clicking opds:// links would open Thorium but fail to
import the catalog. Also fixes the issue where double-clicking .lcpl files
would focus Thorium but not open the file.
Fixes #3075