Websites from history in "popular websites" section.
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 18/100
Research direction
The payload names no files, tests or entry points, so a newcomer has to locate the address bar autocompletion and the popular websites list in the codebase first. The issue asks for a design decision rather than one change: whether history and bookmarks feed the popular websites list, and how that list replaces autocompletion. Done would mean a maintainer-agreed design, so confirm the approach in the thread before writing code.
Written by the indexing model from the issue text.
Description
If we show also websites from history in popular websites section, and websites from bookmarks, we can choose tp disable autocompletion, because "popular websites" section will do everything autocompletion does and even more. But only main domains, not a distinct webpages.
Advantages of that.
- It will allow to go by click to alternative websites when autocompletion can have only one: for example if you type git you wi be suggested both with gilab and github, while autocompletion cant do more than one simultaniously. Which is already partially working, only with popular websites.
- If you want to search for github, autocompletion will complete it to github.com and you have to remove extra letters to not visit github but search for it.
So i suggest to make popular website section into sort of website database, where you will have initial popular websites and websites that user visited, so it always will be able to suggest corrwct websites, from history, bookmarks or just popular ones, and user will be able to disable autocompletion in adress bar entirelly. Even though autocompletion has its flaws that i described, disabling it currently is not viable untill you have an alternative that is good enough, which is point of this suggestion.
- Dominant language
- Dart
- Stars
- 1k
- Forks
- 41
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from FaFre/WebLibre
-
bug enhancement needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
enhancement needs-triage
Difficulty 3/5 1-2 days Newbie friendliness 60/100
-
enhancement needs-triage
Difficulty 5/5 Over a week Newbie friendliness 8/100
-
bug enhancement needs-triage
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
needs-triage
Difficulty 4/5 1-2 days Newbie friendliness 48/100
Similar issues
-
bug from-telegram platform:windows
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
hiddify/hiddify-app#2592 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
cogwheel0/conduit#1122 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
bannzai/shoppinglist#779 ·
Maintainers usually reply within 1 day
-
Android bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
PostHog/posthog-flutter#731 · 1 comment ·
Maintainers usually reply within 1 day
-
[BUG] JEFIT import fails because # characters are not recognisedPossibly taken A pull request linked to this issue is open or already merged. Openbug
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day