This repository has been archived by the owner on Dec 11, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 975
Delete history entry gets added back #9715
Labels
bug
duplicate
Issue has already been reported
feature/history
needs-info
Another team member needs information from the PR/issue opener.
Comments
100 tasks
Since we're not blocking laptop on non-mobile blocking sync issues, let's punt this to 0.19.x and pull it up if fixed sooner. |
fwiw almost nobody syncs history because that's the default |
I see the same bug on a fresh profile without sync enabled. If you click 'delete history entry', the history entry just gets added back at the bottom of the list. |
Similar behavior reported with #9736 |
diracdeltas
added
the
needs-info
Another team member needs information from the PR/issue opener.
label
Jul 12, 2017
srirambv
changed the title
Delete history entry gets added back when sync is enabled
Delete history entry gets added back
Jul 12, 2017
I think this is a duplicate of #8761. |
@bsclifton quitting and restarting the browser doesn't clear the history unless clear history on exit is set |
closing as duplicate of #8761 since the behavior is the same with and without sync enabled |
diracdeltas
added
duplicate
Issue has already been reported
and removed
feature/sync
labels
Jul 13, 2017
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
bug
duplicate
Issue has already been reported
feature/history
needs-info
Another team member needs information from the PR/issue opener.
Did you search for similar issues before submitting this one?
Yes
Describe the issue you encountered:
Delete history entry gets added back when sync is enabled
Platform & Brave Version (revision SHA):
0.17.9 (Pyramid 0) - Windows 10x64
rev 2606974
Muon 4.1.4
0.17.6 (Pyramid 1) - Debian 8.0
rev 30a3eee
Muon 4.1.2
Steps to reproduce:
Actual result:
Delete history entry gets added back when sync is enabled
Expected result:
Should only delete and not add back
Will the steps above reproduce in a fresh profile? If not what other info can be added?
Yes
Is this an issue in the currently released version?
Not sure need to check on older builds
Can this issue be consistently reproduced?
Yes
Extra QA steps:
1.
2.
3.
Screenshot if needed:
Any related issues:
cc: @bsclifton please change milestone if required
The text was updated successfully, but these errors were encountered: