-
Notifications
You must be signed in to change notification settings - Fork 937
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Suppress report autofill breakage prompt after previous submission #4765
Merged
CDRussell
merged 1 commit into
develop
from
feature/craig/autofill_failure_reporting_suppress_prompt_after_recent_submission
Jul 24, 2024
Merged
Suppress report autofill breakage prompt after previous submission #4765
CDRussell
merged 1 commit into
develop
from
feature/craig/autofill_failure_reporting_suppress_prompt_after_recent_submission
Jul 24, 2024
Conversation
This file contains 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
This was referenced Jul 15, 2024
This stack of pull requests is managed by Graphite. Learn more about stacking. Join @CDRussell and the rest of your teammates on |
6 tasks
bd72f22
to
0766da1
Compare
829fc3d
to
8f32f8b
Compare
12 tasks
0766da1
to
bb2268a
Compare
8f32f8b
to
4abcf30
Compare
CDRussell
commented
Jul 16, 2024
...c/test/java/com/duckduckgo/app/browser/autofill/RealAutofillFireproofDialogSuppressorTest.kt
Show resolved
Hide resolved
bb2268a
to
214cc00
Compare
4abcf30
to
be1b06f
Compare
214cc00
to
be61394
Compare
be1b06f
to
0ecd96a
Compare
be61394
to
215d239
Compare
0ecd96a
to
6856443
Compare
215d239
to
79e1f3a
Compare
6856443
to
3c27911
Compare
79e1f3a
to
7e50b8c
Compare
3c27911
to
d82c980
Compare
7e50b8c
to
43b211b
Compare
d82c980
to
3ba1b6c
Compare
43b211b
to
cab53ce
Compare
3ba1b6c
to
441907a
Compare
cmonfortep
approved these changes
Jul 18, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
cab53ce
to
df0092f
Compare
441907a
to
1ea6432
Compare
df0092f
to
19355d4
Compare
089a034
to
200ae14
Compare
19355d4
to
5c08489
Compare
200ae14
to
0b72da0
Compare
3 tasks
5c08489
to
007fa28
Compare
0b72da0
to
dfa4221
Compare
007fa28
to
98a63dd
Compare
dfa4221
to
760734b
Compare
Merge activity
|
98a63dd
to
a8c228a
Compare
Base automatically changed from
feature/craig/autofill_failure_reporting_data_send
to
develop
July 24, 2024 22:27
760734b
to
1d956fa
Compare
laghee
pushed a commit
that referenced
this pull request
Aug 3, 2024
…4765) Task/Issue URL: https://app.asana.com/0/488551667048375/1207767049586678/f ### Description After submitting an autofill breakage report for a site, the user won't be prompted to send another report for the next _n_ days, where _n_ is a value from remote config (defaulting to `42`). ### Steps to test this PR ℹ️ Local hack to enable feature: In `AutofillSiteBreakageReportingFeature`, set default value to `true` --- - [ ] Manually add a password for fill.dev - [ ] Visit https://fill.dev - [ ] Tap on overflow->Passwords - [ ] Tap on `Report a problem with autofill` and choose to `Send Report` - [ ] Verify you no longer see the "report a problem with autofill" view **Verifying you don't see the prompt again for the exact same site** - [ ] Return to browser - [ ] Tap on overflow->Passwords again. - [ ] Verify you **don't** see the "report a problem with autofill" view - [ ] **[Optional]** set your device date to 2 months into the future then repeat; you should see the report autofill problem view **Verifying another page on same website isn't shown prompt** - [ ] Visit another page on the fill.dev site (e.g., https://fill.dev/form/login-simple) - [ ] Tap on overflow->Passwords again. - [ ] Verify you **don't** see the "report a problem with autofill" view **Verifying on a totally different website you do see the prompt again** - [ ] Visit example.com - [ ] Tap on overflow->Passwords again. - [ ] Verify you **do** see the "report a problem with autofill" view
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.
Task/Issue URL: https://app.asana.com/0/488551667048375/1207767049586678/f
Description
After submitting an autofill breakage report for a site, the user won't be prompted to send another report for the next n days, where n is a value from remote config (defaulting to
42
).Steps to test this PR
ℹ️ Local hack to enable feature: In
AutofillSiteBreakageReportingFeature
, set default value totrue
Report a problem with autofill
and choose toSend Report
Verifying you don't see the prompt again for the exact same site
Verifying another page on same website isn't shown prompt
Verifying on a totally different website you do see the prompt again