Be explicit when performing developer redirects #884
Merged
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.
Please review the release process for BrowserServicesKit here.
Required:
Task/Issue URL: https://app.asana.com/0/856498667320406/1207772445672485/f
iOS PR: duckduckgo/iOS#3084
macOS PR: duckduckgo/macos-browser#2978
What kind of version bump will this require?: Patch
Description:
In case any Navigation extension decides we need to perform developer redirect (to reissue navigation with modified URL) we need to be able to react to that in certain situations (e.g. during attribution detection). For that, we are going to be reusing the existing
didCancelNavigationAction(_, withRedirectNavigations: )
callback.Steps to test this PR:
See macOS PR for test steps.
OS Testing:
Internal references:
Software Engineering Expectations
Technical Design Template