-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
prevent the user from firing device removal multiple times #2629
Labels
feature/sync
priority/P3
The next thing for us to work on. It'll ride the trains.
QA Pass-Linux
QA Pass-macOS
QA Pass-Win64
QA/Yes
release-notes/exclude
Milestone
Comments
cc @rossmoody |
bbondy
added
the
priority/P3
The next thing for us to work on. It'll ride the trains.
label
Dec 20, 2018
The most up to date design spec for Sync can be found right here. |
cezaraugusto
added a commit
to brave/brave-core
that referenced
this issue
Jan 2, 2019
cezaraugusto
changed the title
Remove device modal refinement
prevent user from firing device removal multiple times
Jan 2, 2019
cezaraugusto
changed the title
prevent user from firing device removal multiple times
prevent the user from firing device removal multiple times
Jan 2, 2019
cezaraugusto
added a commit
to brave/brave-core
that referenced
this issue
Jan 2, 2019
cezaraugusto
added a commit
to brave/brave-core
that referenced
this issue
Jan 3, 2019
Verification passed on
Verification passed on
Verified passed with
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
feature/sync
priority/P3
The next thing for us to work on. It'll ride the trains.
QA Pass-Linux
QA Pass-macOS
QA Pass-Win64
QA/Yes
release-notes/exclude
Test plan
See brave/brave-core#1193
Description
#2527 (comment)
#2527 (comment)
we need to prevent user from clicking remove multiple times(sending duplicated delete record) while delete record is sending under the hood. we also need to dismiss the remove modal when user click "Remove"
Test Plan:
The text was updated successfully, but these errors were encountered: