[Fix Bug] <handleAppLink ignores shouldHaltWebNavigation for same-domain app links after first trigger> #7097 #7106
+1
−1
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.
I found the handler and implemented the fix: same-domain navigations now return shouldHaltWebNavigation when an app link is launched.
Summary
Updated DuckDuckGoAppLinksHandler.handleAppLink to consistently respect shouldHaltWebNavigation on subsequent same-domain app links, while preserving alwaysTriggerList behavior.
Contribution by Gittensor, learn more at https://gittensor.io/