Use E-TLD+1 when matching domain for login saves #1222
Merged
+36
−47
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/72649045549333/1209272524872735
iOS PR: duckduckgo/iOS#3943
macOS PR: duckduckgo/macos-browser#3844
What kind of version bump will this require?: Major
Description:
Right now, we will offer to autofill into a page which is considered an E-TLD+1 match.
But we aren’t as good at comparing E-TLD+1 when it comes to considering whether to offer to save it or not.
We should detect we have a domain saved already and don’t offer to save when entering credentials for an equivalent subdomain
This should also apply to other scenarios like offering to update the saved password; we should also consider E-TLD+1 matches
Steps to test this PR:
https://app.asana.com/0/1203822806345703/1209279526650235
OS Testing:
Internal references:
Software Engineering Expectations
Technical Design Template