duckduckgo / duckduckgo/Android
[Bug] DDG bookmarks disappeared - or did they?
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 4.8k
- Forks
- 1.4k
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 170
Description
Describe the bug
With a number of tabs open and moving a bookmark folder to the top, the bookmarks just kept scrolling and never reached the top of the list. Exited out of bookmarks and re-entered - the app indicated that there are now NO bookmarks - there were hundreds with a few dozen folders.
An existing open tab shows that a bookmark for it exists and 'edit bookmark' indicates as available.
When a new tab is opened and a URL keyed in that WAS bookmarked, it too shows 'edit bookmark' as available.
If the bookmarks file is empty / gone - why is DDG offering to edit (at least 2) bookmarks that are somehow now in the same folder?
How to Reproduce
Not sure this fluke could be reproduced other than as outlined above.
Will attempt to retain the current config as long as possible to answer any forthcoming questions / provide files / screenshots.
Expected behavior
As always experienced before, the top of the bookmarks list should have eventually shown up.
Environment
- DDG App Version: 5.220.0
- Device: Pixel 4a
- OS: Android 13 + SU Aug 5, 2023
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in the Android app's bookmarks screen using the reported version, Pixel 4a, and Android 13 environment. Reproduce moving a folder to the top with many tabs and folders, then check whether the list scrolls indefinitely while bookmarks remain editable. Done means the list reaches the top and existing bookmarks remain visible after leaving and reopening bookmarks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100