This repository has been archived by the owner on Feb 20, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Allow the user to remove some, or all of their history #356
Labels
Milestone
Comments
Closed
A/C team needs to build this first |
bbinto
added
the
🙅 waiting
Issues that are blocked or has dependencies that are not ready
label
Feb 1, 2019
vesta0
removed
the
🙅 waiting
Issues that are blocked or has dependencies that are not ready
label
Mar 27, 2019
boek
added a commit
to boek/fenix
that referenced
this issue
Mar 29, 2019
boek
added a commit
to boek/fenix
that referenced
this issue
Mar 29, 2019
boek
added a commit
that referenced
this issue
Mar 29, 2019
Closed
Verified that delete history works. Logged new issues separately. Closing this ticket. |
data-sync-user
changed the title
Allow the user to remove some, or all of their history
FNX3-17109 ⁃ Allow the user to remove some, or all of their history
Aug 11, 2020
data-sync-user
changed the title
FNX3-17109 ⁃ Allow the user to remove some, or all of their history
Allow the user to remove some, or all of their history
May 20, 2022
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
As a user, I want Fenix to delete items from my browsing history so that these items are not discoverable later on this browser.
Acceptance criteria
-I can see a list of URLs I’ve visited in the history section of the Fenix library and delete one site from it.
-I can see a list of every URL I’ve visited in the history section of the Fenix library and delete the entire list at once.
-I can leave the library and return to the library and I will not see the URL
-I do not see this URL when I begin typing an exact match on part of the URL in the awesome bar.
-If I delete this URL from my history while the session window in which I accessed it originally is still active, I will not be able to access the URL using the browser’s back button.
┆Issue is synchronized with this Jira Task
The text was updated successfully, but these errors were encountered: